Every broken integration is a lost booking.
Before any API serves real reservations across our brands, it passes The Experience Standard: a continuous, evidence-based certification of production readiness. We test, score, and re-test every connection so that failed bookings do not reach the customer.
Connections fail silently. We make that visible before it reaches a customer.
The experience industry runs on connections, and connections fail silently. An API that passes structural compliance can still time out under reseller load, lose UUIDs across a booking lifecycle, or send pricing that does not match what the customer pays. When that happens, bookings are lost, customers are charged the wrong amount, and the trust between supplier, reseller, and traveller breaks.
The Experience Standard is the mechanism we built to stop that. No integration enters production until it has been tested end to end with real HTTP traffic. And once certified, every integration is re-tested on a fixed cadence for the lifetime of the partnership.
This applies to every API and system that touches a booking inside our group, across all brands and connected systems. Prioticket is the first product to fully publish against the standard; others follow.
Both verified. Different verifications.
Structural compliance
OCTO verifies an API implements the expected endpoints and JSON schema. A passing OCTO badge means the shape is correct.
- · Endpoint presence
- · Schema validity
- · Capability flags
Production readiness
The Experience Standard verifies that an API behaves correctly under real reseller load: SLAs, idempotency, retry safety, commercial fit, and a 90-day regression window before the highest tier is awarded.
- · Availability + booking SLA
- · Retry / idempotency / UUID consistency
- · Commercial alignment
- · 90-day regression history
Four operational areas. Two brand values. Live HTTP traffic.
What it takes to handle real reseller load without dropping bookings.
Does a hold turn into a confirmed booking, return a voucher, and cancel cleanly? UUIDs must be reused across every stage. Cancellation must use POST, not DELETE. We walk the full lifecycle on every run.
Nine deliberate bad requests, every run. Malformed IDs, missing fields, past dates, double-cancels, invalid credentials. The right status code with a parseable error body, every time.
What it takes for partners and resellers to trust what they see.
With the pricing capability requested, do availability and confirmed booking responses carry itemised pricing in minor currency units, with a total and a unit-level breakdown? Mismatched pricing is a customer issue, not an engineering issue.
When a booking is created or cancelled through the API, does your system POST a notification to the receiver within sixty seconds, with the event type and the booking UUID? Without this, resellers must poll.
Awarded by what we observe.
Three tiers, awarded by what we observe. Continuously verified. Held only while earned.
Cleared for live distribution.
Passes our full production-readiness audit. Ready for real bookings.
Cleared for scale.
Verified, with the operational guarantees a high-volume reseller needs.
Cleared for the long run.
Reliable, sustained over ninety days. Awarded by observation, rarely held.
Certification does not end when you pass.
Every certified integration is re-tested on a fixed cadence after issuance, monthly by default. If an API degrades, if a booking SLA slips, if webhook delivery starts failing, the tier is automatically reviewed and demoted before it reaches a customer-facing booking.
The public certificate page for every partner shows the live status of their certification, the date of the last regression run, and the next scheduled run. Anyone with the link can verify the current standing without contacting us.
Built for both ends of the booking.
If you are connecting to an experience-technology integration, the certificate tells you what to expect. The tier sets the operational floor: the higher the tier, the lower the integration risk.
Every certificate is dated and version-bound. You can verify a partner's current standing at any time, with the link or by name.
Every booking you make through one of our brands runs through a certified integration. When the booking confirms, the voucher arrives, the price matches, and the cancellation works, that is The Experience Standard doing its job in the background. The certificate exists so the experience does too.
Look up any partner's current standing.
Enter a partner's certificate slug, or the URL from their certified-by line, to see their current tier, capability badges, and regression status.
Try the demo: view sample certificate.
Common questions.
- Is certification required to work with our group?
- Yes. No integration enters production through any of our brands without a current certificate, at minimum at the Verified tier.
- How long does a certification run take?
- The automated run takes five to ten minutes once the connection details are configured. The end-to-end onboarding (organisation registration, OCTO baseline disclosure, self-declaration, connection setup, first run) typically takes an hour spread across one or two sittings.
- What happens if we fail?
- You receive a detailed report with every failed test, what the runner observed, and what to fix. There is no limit on re-runs. Most partners pass on the second or third attempt after correcting the specific blockers flagged in their first report.
- What does it cost?
- Certification is included in the partnership with our group. There is no separate fee per run, per tier, or per regression cycle.
Start your certification.
Sign up takes a minute. The certification run takes ten.
The Experience Standard is issued by ETG Holding AG, Florastrasse 18a, 8610 Uster, Switzerland.