# FBO (Trip Support Provider)

Manage FBO (Fixed Base Operator) services. These endpoints enable Trip Support Providers to update and retrieve FBO service entries, as well as manage associated documents.

**Note:**  
> FBO services are read-only for properties - only status and remarks can be updated. Creation and deletion are not allowed.


## Get FBO service for a flight - Trip Support Provider scope

 - [GET /api/v2/partners/flights/{flightId}/fbo-services](https://developer.fl3xx.com/reference/v2/fbo-(trip-support-provider)/partnerfboget.md): Retrieves the FBO (Fixed Base Operator) service information for a specific flight within the partner's scope. Returns departure and arrival FBO service entries along with surrounding flight context (previous and next flights) and aircraft details.

Features:
- Returns departure and arrival FBO service entries for the flight
- Includes previous and next flight context for operational awareness
- Includes aircraft details such as type, registration, and MTOW



Note: This endpoint is for Trip Support Providers. Only FBO services associated with the operator linked to the authentication token will be returned.

Example Use Case: A Trip Support Provider retrieves the FBO service details for a flight to review handling requests and confirm service status before departure.

## Update FBO services for a flight - Trip Support Provider scope

 - [PATCH /api/v2/partners/flights/{flightId}/fbo-services](https://developer.fl3xx.com/reference/v2/fbo-(trip-support-provider)/partnerfbopatch.md): Updates the arrival and/or departure FBO service entries for a specific flight.

Features:
- Updates departure and arrival FBO service details including status, aviowikiId, type, request items, and remarks
- Supports partial updates of FBO service information

Note: This endpoint is for Trip Support Providers. Only FBO services associated with the operator linked to the authentication token can be updated.

Partial updates supported: The request body can contain none, one, or both service objects — only the fields provided will be updated. Omitted fields remain unchanged.

Example Use Case: A Trip Support Provider updates the arrival FBO handling requests after confirming services with the ground handler.

## Upload document associated with an FBO service - Trip Support Provider scope

 - [POST /api/v2/partners/fbo-services/{serviceId}/documents](https://developer.fl3xx.com/reference/v2/fbo-(trip-support-provider)/partnerfbodocumentpost.md): Uploads a document file to be associated with an FBO service. Maximum file size is 5 MB.

## Get document associated with an FBO service - Trip Support Provider scope

 - [GET /api/v2/partners/fbo-services/{serviceId}/documents/{uuid}](https://developer.fl3xx.com/reference/v2/fbo-(trip-support-provider)/partnerfbodocumentget.md)

## Delete document associated with an FBO service - Trip Support Provider scope

 - [DELETE /api/v2/partners/fbo-services/{serviceId}/documents/{uuid}](https://developer.fl3xx.com/reference/v2/fbo-(trip-support-provider)/partnerfbodocumentdelete.md)