OCTO Developer Hub
OCTO WebsiteOpenAPI (Swagger)Become a Member
  • Welcome
  • Getting Started
    • Glossary of Terms
    • Errors
    • Headers
    • Authentication
    • Endpoints & Capabilities
    • Schemas
    • Development Support
  • OCTO API Core
    • Supplier
    • Products
    • Availability
    • Bookings
  • Capabilities (Optional)
    • Pricing
    • Notifications
    • Content
    • Pickups (Proposed Draft)
    • Promotions (Proposed Draft)
  • Additional Resources
    • Validation Tool
    • Postman Collections
    • Known Implementations
Powered by GitBook
On this page
  • Request Headers
  • Response Headers

Was this helpful?

  1. Getting Started

Headers

PreviousErrorsNextAuthentication

Last updated 6 months ago

Was this helpful?

A set of HTTP headers must be set when making a request to OCTO API.

These headers can include both standard HTTP headers as well as some custom OCTO API headers. Below are the standard request headers and OCTO custom headers that are required to use:

Request Headers

Header
Required
Description

Authorization

Required

Your Bearer token.

Content-Type

Required

This must be application/json for all POST PATCH and DELETE requests.

Octo-Capabilities

Required

A list of the Capabilities (their IDs) to be included in the response. See to learn more about Capabilities.

Response Headers

Header
Required
Description

Content-Type

Required

application/json

Octo-Capabilities

Required

A list of the Capabilities (their IDs) initialized with your request. See to learn more about Capabilities.

Authentication
Endpoints and Capabilities
Endpoints and Capabilities