# For Developers and Vendors (/docs/guides/developers)



careCycle exposes a public API for everything an integration needs: customers,
policies, campaigns, inquiries, sources, custom fields, and bulk Medicare and
ACA data syncs.

<Cards>
  <Card title="API Reference" href="/docs/api-reference">
    Full endpoint documentation: authentication, customers, policies,
    campaigns, sources, syncs, and more.
  </Card>

  <Card title="Webhook Events" href="/docs/api-reference/webhooks">
    Subscribe to platform events and see delivery payloads.
  </Card>

  <Card title="Customers Who Share a Phone Number" href="/docs/guides/developers/shared-phone-numbers">
    Add a spouse or family member on a customer's number when create returns
    a 409, with safe retries.
  </Card>

  <Card title="Ping-Post Vendor Integration" href="/docs/guides/developers/ping-post-vendor-integration">
    For call vendors: ping for agent availability before transferring a live
    caller. This page is public and does not require a careCycle login.
  </Card>
</Cards>

Common Integrations [#common-integrations]

* **Book of business sync**: push customers and policies from your CRM or
  enrollment platform with the [Medicare
  sync](/docs/api-reference/sync/sync-medicare-customers-and-policies) and
  [ACA sync](/docs/api-reference/sync/sync-aca-customers-and-policies)
  endpoints. Both are upserts, so re-syncing is safe.
* **Lead delivery**: create customers and leads via the API to trigger
  speed-to-lead campaigns.
* **Ping-post call transfers**: vendors check agent availability in real time
  before transferring a caller.

API keys are created by your organization admin in **Settings > Developer >
API Keys**. Guides for API key management and the webhooks UI are coming to
this section.

Questions or a CRM we should integrate with natively? Email
[integrations@carecycle.ai](mailto:integrations@carecycle.ai).