Changelog
This page provides a detailed history of all updates, enhancements, and bug fixes made to our APIs.
Stay informed about the latest changes and plan your integrations accordingly.
[1.3.0] - 2025-03-28
Added
- No additions.
Changed
Travel Authorization Enhancements
Endpoints Affected
GET /api/external/flight/{flightId}/visa
PUT /api/external/flight/{flightId}/visa
Summary of Changes
1. Request & Response Schema Updates
Both crew and passenger objects now include two new nested objects:
travelAuthorizationDeparture
:- New field representing travel authorization status for departure.
- Structure:
{ "status": "RED", "note": "string", "source": "API" }
travelAuthorizationArrival
:- Overrides the existing outer
status
,note
, andsource
fields. - Structure:
{ "status": "GRAY", "note": "string", "source": "API" }
- Overrides the existing outer
Outer fields (
status
,note
,source
) are still present for backward compatibility.
2. PUT /api/external/flight/{flightId}/visa
- Backward compatibility logic:
- If
travelAuthorizationArrival
is missing but outerstatus
,note
, andsource
are present, the system will copy those outer values intotravelAuthorizationArrival
.
- If
3. GET /api/external/flight/{flightId}/visa
- The system will replicate values from
travelAuthorizationArrival
to the outerstatus
,note
, andsource
fields for backward compatibility.
Notes
- These changes are non-breaking for existing clients that rely on the outer fields.
- Developers are encouraged to transition to using the new nested objects for better clarity and future-proofing.
Deprecated
- No deprecations.
Fixed
- No fixes.
Removed
- No removals.
[1.2.0] - 2025-02-28
Added
Crew Expenses: Added
GET /api/external/crew-expenses
endpoint to retrieve a list of expenses associated with crew members.- Business Importance: This addition is crucial for finance managers and accounting departments to efficiently track and manage crew expenses. It ensures that all expenses are accounted for and within the budget, providing a comprehensive overview of crew-related expenditures.
- Use Case: A finance manager wants to review all expenses submitted by crew members for a specific month. By using this endpoint, they can fetch a comprehensive list of expenses, filter them by date, and analyze the data to ensure all expenses are accounted for and within the budget.
Crew Expenses: Added
GET /api/external/crew-expenses/{crewExpenseId}/documents/{documentUuid}
endpoint to download a document associated with a specific crew expense.- Business Importance: This feature is essential for auditing and verification purposes. It allows finance managers to access and review receipts and other documents related to crew expenses, ensuring transparency and accuracy in financial records.
- Use Case: A finance manager needs to review the receipts submitted by a crew member for a specific expense. By using this endpoint, they can download the receipt document associated with the crew expense for further review and verification.
Changed
- No changes.
Deprecated
- No deprecations.
Fixed
- No fixes.
Removed
- No removals.
[1.1.0] - 2025-02-24
Added
- Flight Fuels: Added
POST /api/external/flight/{flightId}/fuels/{fuelId}/documents
endpoint to upload fuel documents for a flight. - Flight Fuels: Added
POST /api/external/flight/{flightId}/fuels/{fuelId}/documents/release
endpoint to upload fuel release documents for a flight. - Flight Fuels: Added
GET /api/external/flight/{flightId}/fuels/{fuelId}/documents/{documentId}
endpoint to download fuel documents or fuel release documents for a flight. - Flight Fuels: Added
DELETE /api/external/flight/{flightId}/fuels/{fuelId}/documents/{documentId}
endpoint to delete fuel documents or fuel release documents for a flight.
Changed
- Flight Fuels: The response body for
GET /api/external/flight/{flightId}/fuels
has been updated to include properties for fuel and fuel release documentsdocuments
andfuelReleaseDocument
.
Deprecated
- No deprecations.
Fixed
- No fixes.
Removed
- No removals.
[1.0.0] - 2025-01-01
- This changelog tracks changes made to the FL3XX API from January 01, 2025 onwards.