### Getting Started Source: https://docs.opentable.com/index Steps required to register as an OpenTable integration partner and gain access to API environments. ```APIDOC ## Getting Started To access OpenTable APIs, you must register and be approved as an integration partner via https://www.opentable.com/restaurant-solutions/api-partners/become-a-partner/. Upon approval, you will be granted access to a Sandbox environment for testing. ``` -------------------------------- ### Environments Source: https://docs.opentable.com/index Details on the available integration environments (Sandbox and Production) and their usage. ```APIDOC ## Environments OpenTable offers two integration environments: Sandbox (pre-production) and Production. ### Sandbox Environment Accessible to approved partners for testing API integrations. Available APIs include Authorization, Directory API, and Sync API. Restaurant IDs for the Sandbox environment will be provided in the partner welcome email. **Note:** The sandbox environment is for development and testing only and should not be used for live integrations. ``` -------------------------------- ### Platform Basics Source: https://docs.opentable.com/index Details on authorization, communication protocols, and request formatting for OpenTable APIs. ```APIDOC ## Platform Basics ### Authorization OpenTable uses OAuth 2.0 for authorization. An access token must be obtained and submitted with all requests. ### HTTPS All OpenTable Partner APIs can only be accessed via HTTPS. ### Content Negotiation Data is exchanged in JSON format. Clients should specify `application/json` in the `Accept` header for all requests. ### Compression OpenTable's Partner Network APIs support LZ4 encoding. Clients should specify `lz4` via the `Accept-Encoding` HTTP header. ### Unique Request Ids All POST, PUT, and PATCH requests must include a unique `X-Request-Id` header for idempotent processing. ``` -------------------------------- ### SSL/TLS Support Source: https://docs.opentable.com/index Information regarding OpenTable's SSL/TLS requirements and supported protocols. ```APIDOC ## SSL/TLS Support OpenTable utilizes Akamai as a CDN partner and supports strong ciphers. OpenTable supports TLS 1.3 for all API communication. Ensure your systems are upgraded to maintain secure connectivity. ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.