> ## Documentation Index > Fetch the complete documentation index at: https://docs.anny.co/llms.txt > Use this file to discover all available pages before exploring further. # Get available end times for a start time > Given a start datetime, returns available end time intervals. ## OpenAPI ````yaml /developers/openapi/customer.openapi.json get /api/v1/availability/end openapi: 3.1.0 info: title: customer-api version: '1.0' contact: name: anny GmbH url: anny.co email: support@anny.co description: >- The Customer API is the **public booking surface** for end-user facing applications. It covers everything a customer can see and do — searching availability, placing bookings, managing their account, and more. --- ## When to use the Customer API Use the Customer API when you are **building something your customers interact with directly**: - **Custom booking flow** — embed a fully branded booking experience inside your own app or website instead of redirecting to anny - **Headless checkout** — drive the cart, checkout, and payment steps entirely from your own frontend - **Custom confirmation pages** — retrieve booking and order details after checkout to render a tailored confirmation - **Opening hours and availability on public pages** — display live schedule data on your website with no authentication required - **White-label experiences** — build lobby screens, kiosks, or mobile apps on top of the Customer API Many endpoints work **without any authentication**. For a custom OAuth2 client to authenticate your own users, contact [support@anny.co](mailto:support@anny.co) with your use case. --- ## Authentication — Optional Auth Most Customer API endpoints work without a token. Providing a customer bearer token unlocks personal data and additional actions: | Auth state | What's accessible | |---|---| | Anonymous | Availability, public resource/service info, booking lookup by number, checkout | | Customer token | Own bookings, account data, communities, passes, queue tickets | ``` Authorization: Bearer {customer_access_token} ``` To authenticate your own users, you need a custom OAuth2 client — contact [support@anny.co](mailto:support@anny.co). See the [Authentication guide](/developers/guides/authentication) for the full token flow. --- ## Customer API vs Admin API | Feature | Customer API | Admin API | |---|---|---| | **Use case** | End-user apps, booking widgets | Server-side automation, backend tooling | | **Auth** | Optional — many endpoints work without a token | Required — API token or OAuth2 | | **Identifiers** | Slugs, booking numbers, order numbers | Immutable UUIDs and integer IDs | | **Access** | Public and customer-owned data only | Full read/write | → [Go to the Admin API](/developers/api-reference/admin) --- ## Resource Identifiers The Customer API uses **human-readable identifiers** that appear in booking URLs: | Entity | Identifier | Example | |---|---|---| | Resources | Slug | `conference-room-berlin` | | Services | Slug | `hourly-desk-booking` | | Organizations | Slug | `acme-gmbh` | | Bookings | Booking number | `BB123456789` | | Orders | Order number | `BO123456789` | Use the Admin API if you need immutable internal IDs for storage in external systems. --- ## Starting Points | Guide | What it covers | |---|---| | [Getting Started](/developers) | First steps and quickstart | | [JSON:API Conventions](/developers/guides/json-api-conventions) | Request and response format | | [Authentication](/developers/guides/authentication) | Customer token flow, OAuth2, anonymous access | | [Availability & Booking Search](/developers/guides/availability) | Search open slots, filter by service and resource | | [Customer Booking Lifecycle](/developers/guides/customer/booking-lifecycle) | View, modify, and cancel bookings | | [Order & Checkout Flow](/developers/guides/customer/checkout) | Cart, checkout steps, payment | | [Plans & Subscriptions](/developers/guides/customer/plans-subscriptions) | Membership plans and recurring billing | | [Communities & Access Control](/developers/guides/customer/communities) | Community membership and access gates | | [Waitlist](/developers/guides/customer/waitlist) | Join and manage waitlists | --- ## Base URLs | Environment | URL | |---|---| | Production | `https://b.anny.co` | | Gov-Cloud | `https://b.anny.eu` | termsOfService: https://anny.co/terms-of-use x-logo: url: https://cdn.anny.co/cms/anny_logo_main_colour_blue_4865e76654.svg altText: anny logo href: https://anny.co servers: - url: https://b.anny.co description: Production - url: https://b.anny.eu description: Gov-Cloud security: [] tags: - name: Account Passes - name: Account Skills - name: Addresses - name: Availability - name: Booking Bundles - name: Booking Passes - name: Booking Quota Grants - name: Bookings - name: Communities - name: Community Accounts - name: Community Invites - name: Customer Accounts - name: Favorites - name: Orders - name: Organizations - name: Plan Subscriptions - name: Properties - name: Queues - name: Queue Tickets - name: Resources - name: Services - name: Waitlist paths: /api/v1/availability/end: get: tags: - Availability summary: Get available end times for a start time description: Given a start datetime, returns available end time intervals. operationId: availability-end-intervals parameters: - name: date_time in: query description: Start datetime (ISO 8601) schema: type: string required: true - name: service_id in: query description: Service UUID schema: type: string required: true - name: resource_id in: query description: Resource UUID schema: type: string - name: adhoc in: query description: Whether this is an ad-hoc booking schema: type: boolean responses: '200': description: Array of end intervals content: application/json: schema: type: array items: $ref: '#/components/schemas/validated-interval.v1' components: schemas: validated-interval.v1: $schema: https://json-schema.org/draft/2020-12/schema x-version: 1.1.0 title: Validated Interval type: object x-tags: - Models description: >- Extended availability interval with full metadata. Used by newer availability endpoints. Includes compatibility fields (`date_time`, `local_date_time`, `next_end_date`) for backwards compatibility with older interval-based endpoints. properties: start_date: type: string format: date-time description: Interval start (W3C / ISO 8601) end_date: type: string format: date-time description: Interval end (W3C / ISO 8601) unit: type: string description: Duration unit of the interval enum: - minute - hour - day - week - month available: type: boolean description: Whether this interval is available for booking number_available: type: integer description: Total number of available slots remaining_number_available: type: integer description: Remaining slots after existing bookings quota: type: integer nullable: true description: Maximum bookable slots (null if unlimited) unavailability_type: type: string description: Reason the interval is unavailable resource_ids: type: array items: type: string description: IDs of resources available for this interval messages: type: array items: type: string description: Human-readable messages about availability constraints series_periods: type: array nullable: true items: type: object properties: id: type: string start: type: string format: date-time end: type: string format: date-time title: type: string description: Series period definitions (for series bookings) timeslot_series_id: type: string nullable: true description: Associated timeslot series UUID title: type: string nullable: true description: Display title for the interval date_time: type: string format: date-time description: >- Compatibility: same as start_date (or end_date for end-interval requests) local_date_time: type: string format: date-time description: 'Compatibility: interval datetime in the resource''s local timezone' next_end_date: type: string format: date-time nullable: true description: 'Compatibility: same as end_date (null for end-interval responses)' ````