Inside Labs API
Welcome to the Inside Labs developer portal. Our platform powers personalised, event-driven experiences for tourism destinations — aggregating activities, memberships, bookings and engagement campaigns behind a single, consistent API surface.
This portal is your one-stop reference for integrating with us.
How it works
The platform is split into independent domains (engagement, event, membership, …). Every domain exposes its own REST API, but you talk to them all through a single base URL and select the domain via the URL path.
https://api.insidelabs.io/{domain}/{path}
Two things are always required on every request:
| Header | Purpose |
|---|---|
Authorization | Bearer <access-token> — see Authentication |
x-omni-tenant | Identifies which tenant (destination) you are operating against |
Environments
| Environment | API base URL | OpenAPI spec |
|---|---|---|
| Development | https://api.dev.insidelabs.io | https://shared-docs-api-specs-develop.s3.eu-central-1.amazonaws.com/apis.json |
| Production | https://api.insidelabs.io | https://shared-docs-api-specs-production.s3.eu-central-1.amazonaws.com/apis.json |
Use development for integration work. We will give you credentials scoped to a development tenant before you go to production.
Quick start
-
Get credentials — request an OAuth
client_id/client_secretand yourtenantidentifier from the Inside Labs team. -
Exchange them for a token — see Authentication.
-
Call an API — for example:
GET https://api.insidelabs.io/engagement/campaigns
Authorization: Bearer <access-token>
x-omni-tenant: <your-tenant> -
Subscribe to events (optional) — see the Event Registry to react to changes in real time.
Where to next
- Domains — what's available today and what's coming.
- Authentication — OAuth client credentials flow.
- Event Registry — subscribe to platform events.
- Universal User ID — how we identify users.
- API Reference — full OpenAPI reference, generated from the live spec.