Update TST
Update TST (Transitional Stored Ticket) pricing for PNR itinerary. This endpoint allows updating pricing information for corporate account bookings.
Endpoint
- URL:
/api/v1/flight/updatetst - Method:
POST - Auth Required: Yes (Bearer Token/X-API-KEY)
- Content-Type:
application/json
Authentication
This endpoint requires a valid JWT Bearer token in the Authorization header:
Authorization: Bearer <access_token>
Obtain tokens via /api/v1/sign-in (POST) with your credentials.
Request Structure
| Field | Type | Required | Description |
|---|---|---|---|
| system | string | No | Booking system code (e.g., VN, VJ, 1A) |
| bookingCode | string | No | Booking code (PNR) |
| caCode | string | No | Corporate account code |
Example Request:
{
"system": "VN",
"bookingCode": "ABC123",
"caCode": "CORP001"
}
Request Constraints & Business Rules
- The booking must exist and be in a valid state for TST updates.
- Corporate account code must be valid and active.
- TST updates are typically used for corporate pricing arrangements.
- Only certain booking statuses allow TST modifications.
- Corporate account discounts and negotiated rates are applied during TST updates.
- The system must support corporate account functionality.
Response Structure
| Field | Type | Nullable | Description |
|---|---|---|---|
| system | string | Yes | System name (e.g., VN, VJ, 1A) |
| status | boolean | No | true if successful, false if failed |
| error | object | Yes | Error details (if any) |
| description | string | Yes | Error description (if any) |
| trackingId | string | Yes | Tracking ID for request logs |
| trackingTime | string | Yes | Time for request tracking (ISO 8601 format) |
Error Object
| Field | Type | Nullable | Description |
|---|---|---|---|
| id | integer | No | Error code ID |
| message | string | Yes | Error message |
Example Response:
{
"system": "VN",
"status": true,
"error": null,
"description": null,
"trackingId": "abc-123",
"trackingTime": "2024-06-01T12:00:00Z"
}
Error Codes
See Error Codes for details on possible error responses.
Security & Validation
- All input is validated for type and required fields.
- Only authenticated users can access this endpoint.
- Booking codes are verified against existing bookings.
- Corporate account codes are validated against authorized accounts.
- All TST updates are logged and traceable.
- Access control ensures only authorized users can update TST pricing.
Validation Questions
- What are the requirements for corporate account setup and validation?
- How are negotiated rates applied during TST updates?
- Are there restrictions on which bookings can have TST updates?
- How does TST pricing differ from standard fare pricing?
For integration support, see Contact Support.