1. Ticketing
PKFARE Flight Buyer API
  • Guides
    • Quick Start
    • Tricks for Playing with PKFARE API
    • Book air tickets with ancillaries
    • Raise refund requests
    • Raise change requests
    • Receive flight rescheduled notification
    • Add Paid Bags after the Booking
    • Branded Fare Integration Guide
  • API Reference
    • Air ticket booking APIs
      • TicketIssuanceNotify_V2
      • Shopping V10
      • PrecisePricing V12
      • Penalty V4
      • PreciseBooking V8
      • CancelOrder
      • OrderPricing V6
      • Ticketing
      • OrderDetail V14
      • RequestTicketing
      • ModifyOrderStatus
    • Ancillary booking APIs
      • AncillaryStatusPush
      • AncillaryPricing V6
      • AncillaryBooking
      • CancelAncillaryOrder
      • AncillaryTicketing
      • AncillaryOrderDetail
    • Flight schedule change APIs
      • ScheduleChangeNotify
      • GetScheduleChangeReply
      • GetScheduleChangeList
      • AcknowledgeScheduleChange
      • AcceptScheduleChange
    • Refund APIs
      • RefundResultNotify
      • ReimbursedResultNotify
      • Refund Pricing
      • CheckRefundPricing
      • RefundRequest
      • CheckRefund
      • CheckReimbursed
      • DownloadAttachmentFile API
      • UploadAttachmentFile API
    • Change APIs
      • ChangeResultPush
      • Change Reshop
      • Change Request
      • Change Passenger Info
      • Change Reprice
      • ChangeRepricePush
    • Void APIs
      • ReimbursedResultPush
      • VoidRequest
    • Cache APIs
      • CacheShopping
      • ValidateItinerary API
    • APIs with all versions
      • CheckInInfoPush
      • Raise change requests Copy
      • Shopping
        • Shopping
        • Shopping_V2
        • Shopping_V4
        • Shopping V7
        • Shopping V9
        • Shopping V8
      • PrecisePricing
        • PrecisePricing
        • PrecisePricing_V2
        • PrecisePricing_V6
        • PrecisePricing V9
        • PrecisePricing V10
        • PrecisePricing V11
      • Penalty
        • Penalty
        • Penalty V2
        • Penalty V3
      • PreciseBooking
        • PreciseBooking
        • PreciseBooking_V2
        • PreciseBooking_V5
        • PreciseBooking V6
        • PreciseBooking V7
      • OrderPricing
        • OrderPricing_V2
        • OrderPricing V4
        • OrderPricing V5
      • Ticketing
        • Ticketing
      • TicketNumPush
        • TicketingNumPush
        • TicketingNumPush_V2
        • TicketingNumPush_V3
        • TicketIssuanceNotify
      • CancelOrder
        • CancelOrder
      • OrderDetail
        • OrderDetail_V2
        • OrderDetail_V3
        • OrderDetail_V4
        • OrderDetail_V5
        • Json_OrderDetail_V7
        • Json_OrderDetail_V8
        • OrderDetail V9
        • OrderDetail V13
      • AncillaryPricing
        • AncillaryPricing
        • AncillaryPricing V5
      • AncillaryBooking
        • AncillaryBooking
      • CancelAncillaryOrder
        • CancelAncillaryOrder
      • AncillaryTicketing
        • AncillaryTicketing_V2
      • AncillaryStatusPush
        • AncillaryStatusPush
      • AncillaryOrderDetail
        • AncillaryOrderDetail
      • RequestTicketing
        • RequestTicketing
      • ScheduleChangeNotify
        • ScheduleChangeNotify
      • GetScheduleChangeList
        • GetScheduleChangeList
      • AcknowledgeScheduleChange
        • AcknowledgeScheduleChange
      • AcceptScheduleChange
        • AcceptScheduleChange
      • GetScheduleChangeReply
        • GetScheduleChangeReply
      • RefundPricing
        • RefundPricing
      • CheckRefundPricing
        • CheckRefundPricing
      • RefundRequest
        • RefundRequest
      • RefundResultNotify
        • RefundResultNotify
      • CheckRefund
        • CheckRefund
      • ReimbursedResultNotify
        • ReimbursedResultNotify
      • CheckReimbursed
        • CheckReimbursed
      • UploadAttachmentFile
        • UploadAttachmentFile
      • DownloadAttachmentFile
        • DownloadAttachmentFile
      • ChangeReshop
        • ChangeReshop
      • ChangeRequest
        • ChangeRequest
      • ChangePassengerInfo
        • ChangePassengerInfo
      • VoidRequest
        • VoidRequest
        • VoidRequest_V2
      • ReimbursedResultPush
        • ReimburseResultPush_V2
  • Development Instructions
    • Signature
    • Order Status Explanation
    • Booking errors explanation and suggestions
    • Price Breakdown Explanation
    • Airlines available from PKFARE
    • PKFARE Operation Notice
    • How to retrieve airlines'PNR and ticket numbers
    • PKFARE Buyer API solutionId Usage Guide
  • Notice
    • Release Note
  • Schemas
    • Schemas
      • ShoppingReq
      • Result«ShoppingResult»
      • Authentication
      • SearchDTO
      • JourneysDTO_1
      • PassengersDTO
      • ShoppingResult
      • SegmentsDTO
      • SolutionsDTO
      • BaggageDTO
      • ConditionsDTO
      • ChangeDTO
      • OtherDTO
      • RefundDTO
      • JourneysDTO
      • SegmentInfoDTO
  1. Ticketing

Ticketing

1 Function#

Through Ticketing API, users can request PKFARE to deduct credits (currently only Prepay and Alipay are supported). Ticket numbers would be provided by TickeitngNumPush or orderDetail API.

2 Versioning#

VersionSandbox Invoking AddressUpdate
ticketinghttps://api.pkfare.com/ticketing
Below is the most updated version.

3 Charater Encoding#

The character code of this API is UTF-8.

4 Request#

4.1 Schema#

Please structure parameter as JSON format. Request should be transmitted after BASE64 encrypted.
NameTypeRequiredDescriptionSample
Authentification
partnerIdstringYesPartner IDRksVSXfZm1yF04adBWYsCD7M4=
signstringYessignature, sign=MD5 (partnerId+partnerKey)17e707b5d9da59065dbb139e5f1bd
ticketing
orderNumStringYes[PKFARE] Order number1012674912
pnrStringYesPNR returned by PreciseBookingKHZ1WU
nameStringNocontact name, formatted with "last name/first name" or "first name"Wang/Jango
emailStringNoemail address [to receive schedule-changed notice]jango.wang@gongfutrip.com
telNumStringNocontact phone number13249073855

4.3 Example#

{
	"authentication": {
		"partnerId": "RksVSX7Pf1yF04adBWYsCD7M4=",
		"sign": "17e707>b5d9dae59065dbb139e5f1bd"
	},
	"ticketing": {
		"email": "jango.wang@gongfutrip.com",
		"name": "Jango/Wang",
		"orderNum": 1012674912,
		"telNum": "13249073855",
		"PNR": "KHZ1WU"
	}
}

5 Response#

5.1 Schema#

NameTypeDescriptionSample
Basic Parameters
errorCodeStringerror code; refer to error code list0
errorMsgStringerror messageOK
dataObjectonly if the errorCode returns "0", returned data would not be null. Data is in JSON format, which contains three collection objects: solutions, flights, segments-
data
orderNumStringorder number in PKFARE system1012704540
orderAmountBigDecimalorder Amount2015.00
transactionExpenseBigDecimalmerchant fee2.02
payAmountBigDecimalactual payment amount2017.02

5.2 Example#

Success response
{
	"errorCode": "0",
	"errorMsg": "ok",
	"data": {
		"orderNum": "1012704540",
		"orderAmount": 2015,
		"transactionExpense":2.02,
		"payAmount": 2017.02
	}
}
Failure response
{
	"errorCode": "P001",
	"errorMsg": "Invalid authentication.",
	"data": null
}

6 Error Code List#

errorCodeerrorMsgDescription
0okrequest has been processed successfully
S001System errorsystem error
P001-wrong parameter
B002Partner is not existspartnerID does not exist
B003Illegal signillegal sign. Please check your signature
B009Order status is invalidorder status is invalid
B010Order number not existorder number does not exist
B022Ticketing failedbalance left is not enough to pay the order
B024Order has been paidorder has already been paid. No need to pay again
Modified at 2024-05-06 01:28:26
Previous
OrderPricing V5
Next
TicketingNumPush