Create an inbound endpoint
Create an endpoint by its full RECEIVE URL — the thing you hand to a provider — which the server resolves back into a domain, slug and path. Two forms, chosen by the host: a SHARED platform domain → https://<platform-host>/<org-slug>/<slug>/<path>; a custom domain → https://<custom-host>/<slug>/<path> (no org segment — the host maps to one org).
The host MUST be one of the org's ingest domains (GET /v1/ingest-domains) — an unknown host is refused with 422 (details.check: url) and never auto-registered; adding a domain is a separate, deliberate flow. On a platform host the org segment is OPTIONAL and filled in when omitted, so https://<platform-host>/<slug> is valid; when present it must be your own org's slug.
Slug uniqueness is per RESOLVED path — unique per-org on a platform domain, per-domain on a custom domain — so a 409 is scoped accordingly (the same slug may exist for a different org, or under a different custom domain).
Authorizations
Scoped API key. Scopes are read ⊂ write ⊂ admin. A call needing more scope than the key holds returns 403 insufficient_scope.
Request Body
Responses
Created.