OCTO Standard v1.0
Bookberry® Engine Integration Gateway
Connect your systems with our OCTO-compliant API for seamless tour and activity bookings
View API Documentation Explore EndpointsSecure Authentication
API Key or JWT Bearer token authentication following OCTO standard security practices.
Real-time Availability
Check product availability in real-time with accurate pricing and capacity information.
Instant Confirmation
Create and confirm bookings instantly with automatic ticket generation.
API Endpoints
Reseller API
For travel agents and resellers to browse products and create bookings.
-
GET
/reseller/octo/v1/products -
POST
/reseller/octo/v1/availability -
POST
/reseller/octo/v1/bookings -
POST
/reseller/octo/v1/bookings/{id}/confirm -
DELETE
/reseller/octo/v1/bookings/{id}
Supplier API
For tour operators to manage their products and incoming bookings.
-
GET
/supplier/octo/v1/products -
GET
/supplier/octo/v1/bookings -
POST
/supplier/octo/v1/bookings/{id}/confirm -
POST
/supplier/octo/v1/bookings/{id}/redeem -
DELETE
/supplier/octo/v1/bookings/{id}
API Versioning
Our API supports multiple versions. Use the version number in the URL path:
/reseller/octo/v1/...- Version 1.0 (current stable)/reseller/octo/v1.2/...- Version 1.2 (upcoming)/reseller/octo/last/...- Always points to the latest version
Tip: Use specific version numbers in production for stability. The
/last/ alias is useful for development and testing.
Authentication
API Key Authentication
Include your API key in the Authorization header:
Authorization: Bearer res_12345678-1234-1234-1234-123456789012API Key Format
- Resellers:
res_{entity_id} - Suppliers:
sup_{entity_id}
Security Note: Never share your API key publicly. Contact support if you believe your key has been compromised.