# Catering (Trip Support Provider) Manage catering services. These endpoints enable Trip Support Providers to create, update, retrieve, and delete catering service entries, as well as manage associated documents. **Note:** > Catering services can be created if the partner is assigned to the flight. Deletion is only allowed if the catering service was created by the partner. ## Get catering services for a flight - Trip Support Provider scope - [GET /api/v2/partners/flights/{flightId}/catering-services](https://developer.fl3xx.com/reference/v2/catering-(trip-support-provider)/partnercateringget.md): Retrieves all catering service entries for a specific flight within the partner's scope. Returns a list of catering service objects including status, assignment, airport, order, pax count, remarks, and associated document UUIDs. Assignment (for): Catering services are only ever assigned to a group, never to an individual person: - "for": {"group": "PAX"} or "for": {"group": "CREW"} — the service applies to the whole passenger or crew group Unlike Hotel and Transport services, per-person assignment ("for": {"person": {...}}) is not supported for catering. Create one catering service for PAX and, if needed, a separate one for CREW. Note: This endpoint is for Trip Support Providers. Only catering services associated with the operator linked to the authentication token can be accessed. Note: This endpoint is for Trip Support Providers. Catering 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 checks which catering orders already exist for a flight before placing a new one. ## Get catering service by ID - Trip Support Provider scope - [GET /api/v2/partners/catering-services/{id}](https://developer.fl3xx.com/reference/v2/catering-(trip-support-provider)/partnercateringbyidget.md): Retrieves the full details of a single catering service by its ID, including status, assignment, airport, order, pax count, remarks, and the metadata of all associated documents. Assignment (for): Catering services are only ever assigned to a group, never to an individual person: - "for": {"group": "PAX"} or "for": {"group": "CREW"} — the service applies to the whole passenger or crew group Unlike Hotel and Transport services, per-person assignment ("for": {"person": {...}}) is not supported for catering. Create one catering service for PAX and, if needed, a separate one for CREW. Note: This endpoint is for Trip Support Providers. Only catering services associated with the operator linked to the authentication token can be accessed. Note: This endpoint is for Trip Support Providers. Catering 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 opens a catering entry to confirm the order details before delivery. ## Update catering service by ID - Trip Support Provider scope - [PATCH /api/v2/partners/catering-services/{id}](https://developer.fl3xx.com/reference/v2/catering-(trip-support-provider)/partnercateringpatch.md): Updates an existing catering service by its ID. Features: - Updates catering service details including status, assignment, order, and remarks - Supports partial updates of catering service information - pax cannot be changed after creation; it is only settable via the create endpoint Assignment (for): Catering services are only ever assigned to a group, never to an individual person: - "for": {"group": "PAX"} or "for": {"group": "CREW"} — the service applies to the whole passenger or crew group Unlike Hotel and Transport services, per-person assignment ("for": {"person": {...}}) is not supported for catering. Create one catering service for PAX and, if needed, a separate one for CREW. 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 catering services associated with the operator linked to the authentication token can be updated. Note: This endpoint is for Trip Support Providers. Catering 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 sets the status to OK once the catering order has been confirmed with the vendor. ## Delete catering service by ID - Trip Support Provider scope - [DELETE /api/v2/partners/catering-services/{id}](https://developer.fl3xx.com/reference/v2/catering-(trip-support-provider)/partnercateringdelete.md): Deletes a catering service by its ID. Note: This endpoint is for Trip Support Providers. Only catering services associated with the operator linked to the authentication token can be deleted. Deletion is only allowed if the catering service was created by the partner; catering services created by the operator cannot be deleted. Note: This endpoint is for Trip Support Providers. Catering 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 removes a catering entry that was created by mistake or is no longer needed. ## Create catering service - Trip Support Provider scope - [POST /api/v2/partners/catering-services](https://developer.fl3xx.com/reference/v2/catering-(trip-support-provider)/partnercateringpost.md): Creates a new catering service for a flight. Features: - Creates a catering service with status, assignment, airport, order, pax count, and remarks - The flight is specified via the required flightId field in the request body — unlike the other catering 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): Catering services are only ever assigned to a group, never to an individual person: - "for": {"group": "PAX"} or "for": {"group": "CREW"} — the service applies to the whole passenger or crew group Unlike Hotel and Transport services, per-person assignment ("for": {"person": {...}}) is not supported for catering. Create one catering service for PAX and, if needed, a separate one for CREW. Note: This endpoint is for Trip Support Providers. Catering 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 places a catering order for the passengers of an upcoming flight. ## Upload document associated with a catering service - Trip Support Provider scope - [POST /api/v2/partners/catering-services/{id}/documents](https://developer.fl3xx.com/reference/v2/catering-(trip-support-provider)/partnercateringdocumentpost.md): Uploads a document file to be associated with a catering service. Maximum file size is 5 MB. Note: This endpoint is for Trip Support Providers. Only catering services associated with the operator linked to the authentication token can be modified. Note: This endpoint is for Trip Support Providers. Catering 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 attaches the vendor invoice to the catering service entry. ## Get document associated with a catering service - Trip Support Provider scope - [GET /api/v2/partners/catering-services/{id}/documents/{documentUuid}](https://developer.fl3xx.com/reference/v2/catering-(trip-support-provider)/partnercateringdocumentget.md): Downloads a document associated with a catering service. The response contains the binary file content. Note: This endpoint is for Trip Support Providers. Only documents of catering services associated with the operator linked to the authentication token can be accessed. Note: This endpoint is for Trip Support Providers. Catering 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 retrieves a previously uploaded invoice to verify the order. ## Delete document associated with a catering service - Trip Support Provider scope - [DELETE /api/v2/partners/catering-services/{id}/documents/{documentUuid}](https://developer.fl3xx.com/reference/v2/catering-(trip-support-provider)/partnercateringdocumentdelete.md): Deletes a document associated with a catering service. Note: This endpoint is for Trip Support Providers. Only documents of catering services associated with the operator linked to the authentication token can be deleted. Note: This endpoint is for Trip Support Providers. Catering 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 removes an outdated invoice after uploading a revised version.