> ## 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. # Update notification read/seen status > Update `read_at` or `seen_at` timestamps on a notification to mark it as read or seen. ## OpenAPI ````yaml /developers/openapi/customer-internal.openapi.json patch /api/v1/notifications/{notification_uuid} 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: Addresses - name: Business Accounts - name: Access Control - name: Connections - name: Notifications - name: Payment Setups paths: /api/v1/notifications/{notification_uuid}: parameters: - schema: type: string format: uuid name: notification_uuid in: path required: true description: UUID of the notification patch: tags: - Notifications summary: Update notification read/seen status description: >- Update `read_at` or `seen_at` timestamps on a notification to mark it as read or seen. operationId: patch-notifications-record parameters: - schema: type: string in: header name: Authorization description: Bearer Token required: true requestBody: content: application/json: schema: type: object properties: data: type: object properties: id: type: string format: uuid type: type: string default: notifications attributes: type: object properties: seen_at: type: - string - 'null' format: date-time read_at: type: - string - 'null' format: date-time examples: mark-read: value: data: id: eb7170b3-2c74-4841-a090-b0c717ce8d6d type: notifications attributes: seen_at: '2023-05-28T17:46:18.261Z' read_at: '2023-05-28T17:46:18.261Z' responses: '200': description: OK content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/notifications.v1' '401': description: Unauthorized '404': description: Not Found security: - Bearer: [] components: schemas: notifications.v1: $schema: https://json-schema.org/draft/2020-12/schema x-version: 1.0.0 title: Notification type: object description: >- An in-app notification for a customer account, covering booking events, subscription changes, and other platform activity. x-tags: - Models properties: type: type: string default: notifications id: type: string format: uuid description: Notification UUID attributes: type: object properties: notifiable_type: type: string description: >- Fully-qualified class name of the notification type (e.g. `App\Notifications\Subscriptions\SubscriptionCreated`) notifiable_id: type: integer description: ID of the notifiable entity data: type: object description: Notification payload properties: title: type: string description: Short notification title message: type: string description: Notification body text additional_lines: type: array items: type: string description: Extra lines of detail text subject: type: object description: The entity this notification is about properties: type: type: string description: JSON:API type of the subject id: type: integer description: ID of the subject action: type: - object - 'null' description: Optional call-to-action link properties: label: type: string url: type: string format: uri read_at: type: - string - 'null' format: date-time description: When the notification was marked as read seen_at: type: - string - 'null' format: date-time description: When the notification was seen (badge cleared) created_at: type: string format: date-time updated_at: type: string format: date-time relationships: type: object properties: notifiable: type: array description: Related notifiable entities links: $ref: '#/components/schemas/links.v1' links.v1: $schema: https://json-schema.org/draft/2020-12/schema x-version: 1.1.0 title: ResourceLinks x-tags: - Models type: object description: JSON:API self-link object properties: self: type: string format: uri securitySchemes: Bearer: type: oauth2 flows: authorizationCode: tokenUrl: https://auth.anny.co/oauth/token refreshUrl: https://auth.anny.co/oauth/token/refresh scopes: {} authorizationUrl: https://auth.anny.co/oauth/authorize ````