Welcome to the core distribution unified suite of Flexi Kayak . This unified framework allows authorized API partners to dynamically extract media resources, inspect real-time seat snapshot inventories, and settle instant isolated booking cycles against their prepaid credit vaults.
All API endpoint requests strictly utilize JSON object communication payloads. Our ingress engines employ anti-tampering non-leakage filters and reject malicious data modifications on impact.
Authentication Gateways & Headers
Ingress validation middleware performs timing-attack protected cryptographic key verification. Missing or illegal header hashes trigger a fast fail-closed block immediately.
🔑 Public Ready-To-Use Test Credentials (Test API Agent 11 - Test Vault Account):
Developers can utilize this public Test API Key directly within request headers during integration and sandbox testing cycles. This token maps explicitly to the credit limits and ledger books of Test API Agent 11 (Demo Sandbox Agent).
Must be exactly mapped to application/json; charset=UTF-8
X-API-KEY
String
Secure client cryptographic hash token provided by the office.
1. Media Content Procurement API
INTEGRATION FLOW - STEP 1: This endpoint serves as the single source of truth for dynamic pricing model resolutions, commissions, cancellations, and multi-tenant identity profiles across both modules. API partners invoke this first to build product catalogs.
🎯 Identity Enforcement Dynamic Parsing Rule:
When the administration updates backend configurations for a specific tour or journey (e.g., the 'Jolly Bouy Island' ferry), the flags inside the identity_enforcement response block update dynamically. The frontend integration layout must render conditional fields accordingly:
is_id_mandatory = 1: Verification documents must be strictly enforced for every passenger payload.
is_id_no_required = 1: Unique document string identifiers (e.g., Aadhaar or Passport numbers) are mandatory input structures.
is_id_upload_required = 1: Valid proof document binary attachments via Base64 stream uploads must be strictly collected.
Query String Mappings
Parameter Key
Type
Status
Operational Bounds
module
String
Required
Strict routing selectors allowed: ACTIVITY or BOAT.
travel_date
String
Required
Target search date string window. Format: YYYY-MM-DD
limit
Integer
Optional
Record packet constraints limit. Bound range: 1 to 500.
2. Live Availability Search Engine
INTEGRATION FLOW - STEP 2: Queries specific target inventory timelines, active slots, remaining capacities, and merchant net rates across independent modules before proceeding to reservation execution.
🛡️ Strict Security & Passenger Validation Guards:
• Foreigner Passport Rule: If the nationality parameter value of any passenger inside the payload is non-Indian (i.e., anything other than INDIAN), the id_type must be strictly passed as PASSPORT, and both id_number and id_proof_file strings are strictly required. Failures will trigger an immediate firewall rejection.
• Base64 Size Bomb Cap: The uploaded document verification binary stream (id_proof_file) must be strictly capped under a length of 2.0 MB.
Master Object Structural Fields
Field Name
Data Type
Status
Validation Metric Requirements
request_id
String
Required
Unique context tracking token. Length cap limit 100 chars.
module_type
String
Required
Explicit processing router targets: ACTIVITY or BOAT.
qty
Integer
Required
Strict integer scale range bound between 1 and 100.
travel_date
String
Required
Temporal format string: YYYY-MM-DD (Must be >= Today).
customer_name
String
Required
Primary customer string name. Maximum length boundary: 100 chars.
Numeric validation match sequence check string: ^[0-9]{8,15}$.
availability_id
Integer
Conditional
Mandatory when module_type is ACTIVITY.
slot_id
Integer
Conditional
Mandatory when module_type is ACTIVITY.
schedule_id
Integer
Conditional
Mandatory when module_type is BOAT.
passengers
Array
Conditional
Mandatory only for BOAT bookings. Array size must match qty.
4. Cancellation & Automated Refund Engine
INTEGRATION FLOW - STEP 4: Processes secure cancellation calculations when a passenger requests a cancellation. QUOTE evaluates refunds/charges, while CONFIRM permanent voids records and credits back wallet balances atomically.
Unique tracking identifier to protect against multi-node replay blocks.
booking_ref
String
Required
The alphanumeric PNR reference code received during booking confirmation.
module_type
String
Required
Classification target engine layers: ACTIVITY or BOAT.
action
String
Required
Fixed state control parameters options allowed: QUOTE or CONFIRM.
qty
Integer
Conditional
Mandatory for ACTIVITY module type. Count of seats to release.
passenger_ids
Array
Conditional
Mandatory for BOAT module type. Array of individual traveler IDs.
5. Wallet Balance & Audit Gateway
INTEGRATION FLOW - STEP 5: Retrieves real-time active cash balances, credit facility limits, utilized runways, and lists recent ledger double-entry journal logs securely scoped by your tenant space. Used by finance systems to ensure sync.
INTEGRATION FLOW - STEP 6: Allows distributors to query precise real-time processing, traveler manifests, ledger reconciliations, and refund states of any active or cancelled reservation at any point in the post-booking lifecycle.