API

Public API boundaries, without invented SDK claims.

WA-AAS has an API route; Lead Caravan now has a matching public page that explains what is and is not exposed.

Lead Caravan's public site submits inquiry and booking context through the approved public flow, then routes protected account work through WA-AAS. Private workspace APIs are not exposed from this static site.

For custom integrations, the right next step is a scoped review of the client stack, permission model, and reporting requirements.

  1. Public

    Inquiry intake

    Public forms collect campaign context and route it into the Lead Caravan review workflow.

  2. Secure

    Account handoff

    Login, account creation, reset, and verification continue through secure WA-AAS routes.

  3. Private

    Workspace APIs

    Protected workspace APIs require account access and are not documented as public Lead Caravan endpoints.

  4. Review

    Custom requests

    New API work starts with source, access, and data-handling review before implementation claims.

Request API review Read docs