Spectare API reference endpoints types and error handling

The Spectare API documentation at spectare.ai/docs is a complete technical reference for developers integrating the platform. Every endpoint is documented with request body shapes, response formats, required authentication, and error codes. The reference is updated whenever a new endpoint ships, so it reflects the current state of the API rather than a snapshot.

The conversion section now covers two endpoints side by side. The original POST /api/conversion beacon is authenticated with a signed visitor token and is the right choice when the browser snippet is present. POST /api/conversion/server is authenticated with your org API key and is the right choice when the conversion finishes where the browser cannot see it, for example in a hosted checkout, a booking webhook, or a CRM event. Both endpoints accept goalName, goalType, goalValue, and goalCurrency. The server endpoint additionally accepts an optional variantId for attribution back to the specific arrangement the visitor saw.

Beyond conversions, the reference covers the qualify, assemble, campaign-link, and SSR endpoints, the content API, the confidence report, and the analytics API. Each entry shows a real request and response example so you can verify your integration before writing any code. Rate limits and authentication requirements are listed per endpoint. If you are building a backend integration rather than a frontend one, the server conversion endpoint and the qualify endpoint are the two most relevant starting points.