> For the complete documentation index, see [llms.txt](https://octodocs.peek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://octodocs.peek.com/getting-started/request-access.md).

# Request Access

How to request access to Peek's OCTO API

To request access, please send an email to `ben.smithart@peek.com`. Peek's Product team will reach out to you shortly.

<mark style="color:purple;">**Before you do, please review this FAQ.**</mark> :point\_down:

### Getting access and testing

**Do I need approval to connect as a reseller?**

No. There's no approval process and no agreement with Peek - we just power the API. As long as the connection works (availability comes through, bookings push to Peek Pro successfully), you're free to proceed. Your commercial agreement is with each operator you connect to.

**Is there a sandbox?**

There's a test account in Peek Pro production you can build against, which we'll provide an API key for in our reply to your email.

**Can I get a Peek Pro login for the test account?**

No, unfortunately. Peek Pro logins are limited to operator customers. If you need to verify a test booking on the Peek Pro side, send us the booking ID and we'll spot check it and share a screenshot.

### Connecting to operators

**Is there a global API key or a catalog of all Peek Pro operators?**

No. Each Peek Pro account issues its own API key, so each operator you work with gives you theirs. Operators opt in individually, and which products you can see depends on what each operator sets up for OCTO.

**How does an operator create a key?**

In Peek Pro, under Configuration → OCTO, they use the "Open API" option to create an OCTO connection and key, then hand it to you. Our [help center article](https://help.peek.com/hc/en-us/articles/4412183815444-How-do-I-Create-an-OCTO-Connection-With-Peek-s-Open-API) walks through it. It's behind a Peek Pro login, so operators can open it and you may want to ask them to share it.

**Who in the operator's account can set this up?**

An Admin. Creating OCTO variants and the connection requires the Admin role, so if you're helping an operator set it up, make sure whoever is in the account has that role before you start.

**My client isn't on Peek Pro yet. What do they do?**

They can [request a demo on peek.com](https://www.peek.com) - that's the best way to get them into our sales process and in front of the right people. Once they're on Peek Pro, the steps above apply.

**Once I've built my integration, can I connect with any operator?**

Yes. Once you're comfortable with your implementation, you're free to connect with any operator who uses Peek Pro and has or is willing to entere a business agreement with you.

### Payments, fees and commission

**Who collects payment on an OCTO booking?**

You do. OCTO isn't built to handle payment - it only serves up availability and receives bookings. The reseller collects payment and is the merchant of record, and then pays the operator per your agreement with them. Peek isn't the merchant of record for OCTO bookings.

**What does Peek charge?**

Resellers aren't charged anything. Peek charges the *operator* a 3% fee on OCTO bookings, per the Reseller Hub clause in our [Terms & Conditions](https://www.peek.com/terms).

**Do I owe a fee if I only read availability?**

No. The fee only applies when an OCTO booking is created. Reading products and availability is free for you and the operator.

**How is my commission determined?**

Between you and each operator. Peek isn't a party to that contract, and the partnership agreement lives between you and the operator.

### What our OCTO implementation does and doesn't support

**Can I use OCTO only for availability and send guests to the operator's checkout to book?**

Yes, but OCTO wasn't built around a "get availability from OCTO, book in the operator's widget" model. It's tricky to pull off and usually not the best traveler experience.

**Can I collect custom booking questions?**

No, our OCTO implementation doesn't support custom questions yet - but that'll come in the future.

**How do waivers work?**

Travelers get the confirmation email the operator has set up in their Peek Pro account. If the operator requires a waiver, that email often includes the link to sign it.

**Can I get min and max age on ticket types?**

Not today. Peek Pro doesn't have min/max age fields, only a ticket type (Adult, Senior, etc.). Operators put age ranges in the ticket name instead (like "Child | Ages 3 - 11"), so `restrictions.minAge` and `maxAge` come back as null.

### Webhooks and staying in sync

**Does availability reflect bookings from the operator's other channels?**

Yes. Availability comes straight from the operator's Peek Pro account, so it reflects what's booked there regardless of source.

**Will OCTO webhooks tell me about bookings from other channels?**

No. [OCTO webhooks](https://octodocs.peek.com/capabilities/webhooks) are self-enabled through the API, but they only fire for bookings created through your API key for that operator. Peek's [native webhook events](https://peek.gitbook.io/webhooks) fire for every booking in a Peek Pro account, wherever it came from.
