Replify exposes HTTP APIs so you can integrate phone and campaign workflows with your own systems. This section covers how to authenticate, manage keys, and which APIs are available today.Documentation Index
Fetch the complete documentation index at: https://docs.replify.ai/llms.txt
Use this file to discover all available pages before exploring further.
Authentication
All current Replify APIs use the same authentication model:- Send your API key secret in the
x-api-keyheader on every request. - API Gateway validates the key and routes the request to your organization.
https://api.heylibby.com/api/v1
Individual API pages document paths, payloads, and responses. The legacy Outbound Phone Calling API uses a different auth flow and is being retired.
API keys
Create and manage keys in the portal — you do not need to contact support.- Open in your organization settings.
- Click + Create new API key and give it a descriptive name (e.g. “CRM integration” or “Outbound calls”).
- Copy the secret key immediately and store it in your password manager, secrets store, or integration config.
Available APIs
Migrating from the legacy outbound API? If you use the legacy Outbound Phone Calling API, switch to the current API by July 1, 2026. Your account manager can help with endpoint and testing changes.
Outbound Phone Calling
Schedule a single immediate outbound call for an assistant — testing, demos, or one-off dials.
Campaign Service
Add, update, or remove contacts in campaigns programmatically.
x-api-key authentication unless noted otherwise on its reference page.