Endpoints & Capabilities
Ventrata supports all OCTO Core endpoints plus optional capability extensions.
This page documents the reseller-facing octo/* capability set from the API source (dashboard/app/controllers/apis/octo_controller.rb and dashboard/app/controllers/apis/octo/*_capability.rb).
OCTO Core Endpoints
Core endpoint routes are documented in these pages:
List non-internal capabilities available from the API.
Successful response
Capability ID to include in the Octo-Capabilities header.
octo/waiversSupported capability revision.
1Whether this capability is required for the product.
falseCapability IDs required when this capability is requested.
Capability documentation URL.
https://docs.ventrata.com/capabilities/waiversGET /octo/capabilities HTTP/1.1
Host: api.ventrata.com
Accept: */*
Successful response
[
{
"id": "octo/waivers",
"revision": 1,
"required": false,
"dependencies": [],
"docs": "https://docs.ventrata.com/capabilities/waivers"
}
]Return supplier, connection, and partner context for the current API key.
Successful response
Connection identifier.
conn_reseller_west_coastPartner value.
reseller_partnerList of capability values.
["octo/pricing","octo/offers","octo/waivers"]GET /octo/whoami HTTP/1.1
Host: api.ventrata.com
Accept: */*
Successful response
{
"supplier": {
"id": "3d6f0a3a-59d4-4b16-a0c5-11d2d8a4e6b7",
"name": "City Sightseeing Group",
"reference": "CITY_SIGHTSEEING_GROUP",
"website": "https://www.city-sightseeing.com",
"contact": {
"website": "https://www.city-sightseeing.com",
"email": "jane.doe@goldengatetours.com",
"telephone": "+12025550123",
"address": "123 Main St, San Francisco, CA"
},
"endpoint": "https://hooks.example-partner.com/octo/webhook"
},
"connectionId": "conn_reseller_west_coast",
"partner": "reseller_partner",
"capabilities": [
"octo/pricing",
"octo/offers",
"octo/waivers"
]
}octo/* Capability Coverage
octo/waivers
No
Waiver templates on products and waiver submission/status fields on booking and unit-item flows.
octo/redemption
No
Redemption lookup, redeem/unredeem, no-show, and credential resolution flows.
Capability Object Shape
Capabilities returned on product payloads and /octo/capabilities use this shape:
id
Capability ID to include in Octo-Capabilities.
revision
Supported, backward-compatible capability revision.
required
Whether capability is required to sell that product.
dependencies
Capability IDs that are auto-included when needed.
docs
Documentation URL when provided by the API.
Supplying Capabilities
Send requested capability IDs in the Octo-Capabilities request header on any OCTO endpoint (or X-Capabilities as the legacy alias). Capability IDs are requested uniformly via headers across all endpoints.
The response echoes applied capabilities in the Octo-Capabilities response header.
Last updated