Watch Dealer API & Webhooks

The HoroClick APIHoroClick has a REST API, so a watch dealer or watchmaker can read and write their own records from their own software — or let an AI agent do it. It covers the same data the application does: stock, consignments, clients, sourcing requests, repair jobs and inquiries.EndpointsSix resources, all the same shape: /v1/watches, /v1/consignments, /v1/people, /v1/repair-jobs, /v1/inquiries and /v1/source-tasks. Each takes GET to list or retrieve, POST to create, PATCH to update and DELETE to remove.AuthenticationAn API key created in HoroClick under Profile then API keys, sent as Authorization: Bearer. A key is shown once, carries only the scopes granted to it, and is stored as a SHA-256 hash rather than in plain text.Built for softwareCursor pagination that cannot repeat or skip rows while inventory changes. updated_since for incremental sync. An Idempotency-Key header so a retried create cannot produce a duplicate. Per-key rate limits reported in X-RateLimit headers. Errors carrying a stable code, a plain-language message and a hint naming the fix.WebhooksSubscribe to events instead of polling. Every change emits, whatever caused it — the application, the API, an integration or a scheduled job. Deliveries are signed with HMAC-SHA256 over a timestamped payload, so a captured request cannot be replayed, and failures retry with exponential backoff.For AI agentsThe API describes itself: /api/v1 returns resources and conventions, /api/v1/openapi.json is a full OpenAPI 3.1 specification, and /api/v1/events lists every webhook event. An agent can work out what to call without documentation.The API is included on every paid plan, from $99 per month AUD.