Everything the product does through its own interface is available over a documented REST API with scoped bearer tokens, and everything that happens in it can be pushed to you over signed webhooks. Mint a key at Integrations, then call GET /api/v1/me to confirm your auth before wiring anything else. None of these pages need an account to read.
All 60 operations with the scope each one needs, plus authentication, pagination and rate limits. 17 scopes, so a token can be narrowed to exactly what it needs. Generated from the OpenAPI schema, so it cannot fall behind the API.
The machine-readable spec, for Postman, code generators, or an agent that would rather read a schema than a page.
The envelope, how to verify the HMAC signature, the retry schedule, and all 54 subscribable events. Includes the 14 reserved names that do not fire yet, because a silent integration is worse than a missing one.
Push buying signals in from Clay, Common Room or your own tooling over a signed webhook, and have them become evidence the engine can cite. Includes the exact accounting of what the endpoint can and cannot do, which is a shorter list than you might expect.
One page per RFC 7807 problem type, 17 in total. These are the exact URLs the API puts in the "type" field of an error, and each says whether retrying can ever succeed.
What SealDeal connects to, what each connection actually does, and an explicit list of what it does not integrate with.
How the holdout works: what to randomize, which statistical test, and how optional stopping is prevented.
The reference sections are generated from the same definitions the running code uses: the endpoint tables from the OpenAPI schema, the event lists from the dispatcher catalog, the retry schedule from the delivery worker, and the error pages from the problem types the API actually emits. Tests fail the build if any of them fall out of step. It is worth saying because documentation that quietly disagrees with the system it describes is worse than none: it costs you an afternoon before you stop believing it.
Questions the docs do not answer: hello@sealdeal.ai