Search for flights and return raw PKFare API response without mapping
This endpoint returns the unprocessed PKFare API response, useful for:
- Debugging and understanding the raw data structure
- Testing and development
- Analyzing PKFare response format
Request Parameters
Same as /flights/search endpoint:
- origin (required): Origin airport IATA code (e.g., “DXB”)
- destination (required): Destination airport IATA code (e.g., “MUC”)
- departureDate (required): Departure date in YYYY-MM-DD format
- returnDate (optional): Return date for round-trip flights
- adults (required): Number of adult passengers (minimum: 1)
- children (optional): Number of child passengers
- infants (optional): Number of infant passengers
- cabinClass (optional): Preferred cabin class (economy, business, first)
- nonstop (optional): Only show nonstop flights
- airline (optional): Filter by specific airline code
- maxStops (optional): Maximum number of stops allowed
- maxResults (optional): Maximum number of results (default: 50, max: 100)
- limit (optional): Code-level limit for data returned (internal use)
- sortBy (optional): Sort by price, duration, departure_time, or arrival_time
- sortOrder (optional): Sort order (asc or desc)
- currency (optional): Currency code (e.g., “AED”, “AED”, “EUR”). Defaults to “AED”
Response
Returns the raw PKFare API response structure without any transformation or mapping.
The response structure follows PKFare’s native format with solutions, flights, and segments.
Note
This endpoint is primarily for debugging purposes. For production use, prefer the /flights/search endpoint which returns normalized and mapped data.