# Transport (Trip Support Provider) Manage transport services. These endpoints enable Trip Support Providers to create, update, retrieve, and delete transport service entries, as well as manage associated documents. **Note:** > Transport services can be created if the partner is assigned to the flight. Deletion is only allowed if the transport service was created by the partner. ## Get transport services for a flight - Trip Support Provider scope - [GET /api/v2/partners/flights/{flightId}/transport-services](https://developer.fl3xx.com/reference/v2/transport-(trip-support-provider)/partnertransportsget.md): Retrieves all transport service entries for a specific flight within the partner's scope. Returns a list of transport service objects including status, transport type, assignment, airport, notes, and associated document UUIDs. Assignment (for): Each transport service is assigned either to a group or to one person, never both: - "for": {"group": "PAX"} or "for": {"group": "CREW"} — the service applies to the whole passenger or crew group - "for": {"person": {"id": "...", "name": "..."}} — the service is assigned to a single individual, who can be a passenger or a crew member. person.id is the userId. Note: This endpoint is for Trip Support Providers. Only transport services associated with the operator linked to the authentication token can be accessed. Example Use Case: A Trip Support Provider checks which transport arrangements already exist for a flight before creating a new one. Note: This endpoint is for Trip Support Providers. Transport services can only be created for flights of the operator linked to the authentication token, and only if the partner is assigned to the flight. ## Get transport service by ID - Trip Support Provider scope - [GET /api/v2/partners/transport-services/{id}](https://developer.fl3xx.com/reference/v2/transport-(trip-support-provider)/partnertransportbyidget.md): Retrieves the full details of a single transport service by its ID, including status, transport type, assignment, airport, notes, and the metadata of all associated documents. Assignment (for): Each transport service is assigned either to a group or to one person, never both: - "for": {"group": "PAX"} or "for": {"group": "CREW"} — the service applies to the whole passenger or crew group - "for": {"person": {"id": "...", "name": "..."}} — the service is assigned to a single individual, who can be a passenger or a crew member. person.id is the userId. Note: This endpoint is for Trip Support Providers. Only transport services associated with the operator linked to the authentication token can be accessed. Example Use Case: A Trip Support Provider opens a transport service entry to review its current status and attached confirmation documents. Note: This endpoint is for Trip Support Providers. Transport services can only be created for flights of the operator linked to the authentication token, and only if the partner is assigned to the flight. ## Update transport service by ID - Trip Support Provider scope - [PATCH /api/v2/partners/transport-services/{id}](https://developer.fl3xx.com/reference/v2/transport-(trip-support-provider)/partnertransportpatch.md): Updates an existing transport service by its ID. Features: - Updates transport service details including status, transport type, assignment, and notes - Supports partial updates of transport service information Assignment (for): Each transport service is assigned either to a group or to one person, never both: - "for": {"group": "PAX"} or "for": {"group": "CREW"} — the service applies to the whole passenger or crew group - "for": {"person": {"id": "...", "name": "..."}} — the service is assigned to a single individual, who can be a passenger or a crew member. person.id is the userId. Partial updates supported: The request body can contain any subset of the fields — only the fields provided will be updated. Omitted fields remain unchanged. Note: This endpoint is for Trip Support Providers. Only transport services associated with the operator linked to the authentication token can be updated. Example Use Case: A Trip Support Provider sets the status to OK after the ground transportation has been confirmed with the local supplier. Note: This endpoint is for Trip Support Providers. Transport services can only be created for flights of the operator linked to the authentication token, and only if the partner is assigned to the flight. ## Delete transport service by ID - Trip Support Provider scope - [DELETE /api/v2/partners/transport-services/{id}](https://developer.fl3xx.com/reference/v2/transport-(trip-support-provider)/partnertransportdelete.md): Deletes a transport service by its ID. Note: This endpoint is for Trip Support Providers. Only transport services associated with the operator linked to the authentication token can be deleted. Deletion is only allowed if the transport service was created by the partner; transport services created by the operator cannot be deleted. Example Use Case: A Trip Support Provider removes a transport service entry that was created by mistake or is no longer needed. Note: This endpoint is for Trip Support Providers. Transport services can only be created for flights of the operator linked to the authentication token, and only if the partner is assigned to the flight. ## Create transport service - Trip Support Provider scope - [POST /api/v2/partners/transport-services](https://developer.fl3xx.com/reference/v2/transport-(trip-support-provider)/partnertransportpost.md): Creates a new transport service for a flight. Features: - Creates a transport service with status, transport type, assignment, airport, and notes - The flight is specified via the required flightId field in the request body — unlike the other transport endpoints, the flightId is not part of the URL path - The airport the service applies to is set via the airport object in the request body Assignment (for): Each transport service is assigned either to a group or to one person, never both: - "for": {"group": "PAX"} or "for": {"group": "CREW"} — the service applies to the whole passenger or crew group - "for": {"person": {"id": "...", "name": "..."}} — the service is assigned to a single individual, who can be a passenger or a crew member. person.id is the userId. Note: This endpoint is for Trip Support Providers. Transport services can only be created for flights of the operator linked to the authentication token, and only if the partner is assigned to the flight. Example Use Case: A Trip Support Provider creates a limousine transfer entry for the passengers of an upcoming flight. ## Upload document associated with a transport service - Trip Support Provider scope - [POST /api/v2/partners/transport-services/{id}/documents](https://developer.fl3xx.com/reference/v2/transport-(trip-support-provider)/partnertransportdocumentpost.md): Uploads a document file to be associated with a transport service. Maximum file size is 5 MB. Note: This endpoint is for Trip Support Providers. Only transport services associated with the operator linked to the authentication token can be modified. Example Use Case: A Trip Support Provider attaches the booking confirmation received from the transport supplier to the transport service entry. Note: This endpoint is for Trip Support Providers. Transport services can only be created for flights of the operator linked to the authentication token, and only if the partner is assigned to the flight. ## Get document associated with a transport service - Trip Support Provider scope - [GET /api/v2/partners/transport-services/{id}/documents/{documentUuid}](https://developer.fl3xx.com/reference/v2/transport-(trip-support-provider)/partnertransportdocumentget.md): Downloads a document associated with a transport service. The response contains the binary file content. Note: This endpoint is for Trip Support Providers. Only documents of transport services associated with the operator linked to the authentication token can be accessed. Example Use Case: A Trip Support Provider retrieves a previously uploaded booking confirmation to verify the details. Note: This endpoint is for Trip Support Providers. Transport services can only be created for flights of the operator linked to the authentication token, and only if the partner is assigned to the flight. ## Delete document associated with a transport service - Trip Support Provider scope - [DELETE /api/v2/partners/transport-services/{id}/documents/{documentUuid}](https://developer.fl3xx.com/reference/v2/transport-(trip-support-provider)/partnertransportdocumentdelete.md): Deletes a document associated with a transport service. Note: This endpoint is for Trip Support Providers. Only documents of transport services associated with the operator linked to the authentication token can be deleted. Example Use Case: A Trip Support Provider removes an outdated booking confirmation after uploading a revised version. Note: This endpoint is for Trip Support Providers. Transport services can only be created for flights of the operator linked to the authentication token, and only if the partner is assigned to the flight.