Admin API - anny

The Admin API gives you full programmatic access to your anny organization. It is built for server-side integrations — backend services, automation scripts, and custom tooling that act on behalf of your team.

When to use the Admin API

Use the Admin API when you need to drive workflows from your own systems:

Sync membership data — create or update customers, assign them to communities, reflect subscription status from an external CRM
Create bookings programmatically — build back-office tools or automate repeat reservations without going through the customer checkout
Issue and forward invoices — generate invoices, send them to customers, or push them to your accounting system
React to real-time events — pair the API with Webhooks to trigger side effects whenever a booking is created, cancelled, or checked in
Drive display panels — push live occupancy and schedule data to digital signage or lobby displays

Combined with webhook subscriptions, you can build fully automated, event-driven workflows without polling.

Authentication

Generate a long-lived API token directly in the admin dashboard under Organization Settings → API. All requests require it in the Authorization header:

Authorization: Bearer {access_token}

Every endpoint is organization-scoped. Pass your organization ID as a query parameter on every request:

?o={organization_id}

See the Authentication guide for token scopes and the full OAuth2 flow.

Admin API vs Customer API

	Admin API	Customer API
Use case	Server-side automation, backend tooling	End-user apps, booking widgets
Auth	Required — API token or OAuth2	Optional — many endpoints work without a token
Identifiers	Immutable UUIDs and integer IDs	Slugs, booking numbers, order numbers
Access	Full read/write	Public and customer-owned data only

→ Go to the Customer API

Resource Identifiers

The Admin API uses immutable IDs — UUIDs for most entities, integers for legacy ones. These are safe to store in external systems and never change, even if an organization renames a resource.

Starting Points

Guide	What it covers
Getting Started	First steps and quickstart
JSON:API Conventions	Request and response format
Authentication	API tokens, OAuth2, scopes
Availability & Booking Search	Search open slots and timeslots
Admin Booking Creation	Create bookings from the back office
Admin Booking Lifecycle	Status changes, check-in, cancellations
Invoices	Create, send, and manage invoices
Customer Management	Create and manage customer records
Booking Calendars	Custom calendar events
Timeslot Management	Manage timeslot CRUD, recurrence, allocations, and rescheduling
Broadcast Campaigns	Email and push campaigns
Exports	Export bookings and customer data
Webhooks & Events	Subscribe to real-time events

Base URLs

Environment	URL
Production	`https://b.anny.co`
Gov-Cloud	`https://b.anny.eu`

​When to use the Admin API

​Authentication

​Admin API vs Customer API

​Resource Identifiers

​Starting Points

​Base URLs