Build on Ayalink without crossing trust boundaries

Use the public API, installation-scoped Webhooks, and durable provider protocols, and learn the OAuth 2.0 with PKCE security boundary. OAuth endpoints remain pending security review. Every example fails honestly when an API or capability is unavailable.

Enterprise integration API reference

Public integration paths

End-to-end integration

Move from platform enablement and authorization through API use, Webhooks, testing, production, and emergency revocation, with availability at every stage.

Third-party Storefront

Render public catalog data and send users through the Ayalink authorization domain for account access.

OAuth and PKCE

Official authorization domain, exact redirects, PKCE S256, isolated grants, and phishing recovery; OAuth APIs remain pending review.

Runtime extensions

Signed Webhooks, versioned inventory synchronization, and recoverable automatic fulfillment.