Peek API
Peek publishes a Reseller API at octodocs.peek.com implementing the OCTO industry spec, which Peek helped found. Bearer-token keys are issued on request from Peek, with no published pricing. Webhooks cover booking updates; SDKs are limited to an Elixir starter kit.
Frequently asked questions
Peek scores B+ on the API Report Card. Peek publishes a Reseller API at octodocs.peek.com implementing the OCTO industry spec, which Peek helped found. Bearer-token keys are issued on request from Peek, with no published pricing. Webhooks cover booking updates; SDKs are limited to an Elixir starter kit.
Peek has a workable official integration path. Most engineering teams can build against it directly. Solid API with minor gaps
Peek is the parent company behind Peek Pro, a cloud-based operating system for tours, activities, rentals, and (after a November 2025 acquisition spree) museums, theme parks, and cultural attractions.
Peek targets experience and attraction operators: small-to-mid tour and activity companies (kayak rentals, escape rooms, ghost tours, brewery tours, watersports, axe throwing, adventure guides, climbing gyms), seasonal attractions (haunted houses, pumpkin patches, Christmas events), and, post-acquisition, large cultural institutions and theme parks via the ACME and Connect&GO brands. An operator signs up for Peek Pro, configures activities/rentals/products, time slots, capacity, resources (guides, boats, kayaks, rooms), pricing rules, and policies.
Moderate. Peek is one of the three most-named tours-and-activities reservation platforms in the US, regularly compared head-to-head with FareHarbor (Booking Holdings) and Bokun (TripAdvisor) and showing up against Rezdy, Xola, Checkfront, and ROLLER in buyer-evaluation content.
Peek is headquartered in San Francisco, California. Founded 2012 by CEO Ruzwana Bashir (ex-Blackstone, Oxford, Stanford GSB) and Oskar Bruening. Approximately 264 employees as of January 2026 per Tracxn.
Peek was founded in 2012 in San Francisco by Ruzwana Bashir (CEO) and Oskar Bruening.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.