API documentation

The Vetzy REST API lets you integrate veterinary search, professional profiles and appointment management into third-party applications. It is designed for partners, integrators and veterinary software vendors.

The OpenAPI specification is the source of truth for schemas, parameters and response codes. Review it before any production rollout.

The API uses access tokens (Bearer token) issued via Laravel Sanctum. Each authenticated request must include the header:

Authorization: Bearer <your-token>

Tokens are tied to an API account and a set of permissions (scopes). Never share your tokens in public client code or a versioned repository.

API accounts are not created through public sign-up. To obtain access:

1. Contact Vetzy via the support center describing your use case (integration, estimated volume, environments).
2. A Vetzy administrator provisions your account and associated keys.
3. Request a key with the docs permission to access interactive Swagger documentation.

Interactive documentation: https://api.vetzy.eu/api/docs

All requests use explicit versioning in the path:

https://api.vetzy.eu/v1/

Always use HTTPS in production. Recommended headers:

Accept: application/json
Content-Type: application/json

Exposed resources include:

• Users and profiles — read and update according to your permissions
• Pets — records linked to owners
• Veterinarians and clinics — search and public profiles
• Appointments — create, view and cancel
• Services — consultation types and availability

Refer to the OpenAPI spec for the full list, pagination parameters and available filters.

Rate limiting applies to public and authenticated routes. When exceeded, the API returns 429 Too Many Requests with a Retry-After header.

Client-side best practices:

1. Cache read responses when relevant
2. Implement exponential backoff on 429 and 5xx errors
3. Avoid aggressive polling; prefer webhooks when available

1. Version your integrations on /v1/ — anticipate changes by reviewing the API changelog
2. Validate all input on the client and server
3. Store tokens securely (environment variables, vault)
4. Log correlation IDs to simplify support
5. Test in a development environment before production deployment

Integration questions: Vetzy support center.