Information
- OpenAPI version:
3.1.0
Overview
Every endpoint the Stitch collector serves: the browser's beacon, the server-to-server contracts, and the value model.
Stitch collector API 1.0.0
Section titled “Stitch collector API 1.0.0”Stitch is Beeline’s attribution system. The collector is the one host every integration talks to: the website’s SDK posts page views to it; lead events, loan stages, sessions and the value of an application arrive from whichever system owns each — a CRM, a loan origination system, a portal, an agent platform, or a middleware in front of any of them. Stitch does not know or care which: it sees a key, which names the system the owner issued it to, and a payload.
Two habits apply across the lifecycle endpoints. /v1/conversion takes an idempotency_key and /v1/session an external_session_ref, and re-sending either is harmless (a 200 or the existing id). No payload needs to be complete: send what you have now and more later.
Authentication: /v1/identify, /v1/conversion, /v1/score and /v1/session carry Authorization: Bearer <key>, one key per system, issued by the owner and never sent over chat; /v1/declared takes a key from a system or no key from a registered page. A missing or unknown key is 401 {"error":"unauthorized"} with nothing written. The browser’s endpoints (/v1/collect, /v1/consent, /v1/decorate, /sdk.js) take no key; cross-origin calls to them are allowed only from registered first-party domains.
Authentication
Section titled “ Authentication ”webhookKey
Section titled “webhookKey ”One key per system (vesta, relcu, portal, magicblocks, app), issued by the owner. The system a key belongs to is recorded on every row it creates as source_system.
Security scheme type: http