Overview - AI Assistant

Authentication

All current Replify APIs use the same authentication model:

For endpoints that accept a JSON body, also send:

Content-Type: application/json

Production base URL:https://api.heylibby.com/api/v1Individual 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.

  1. Open API Key Management in your organization settings.
  2. Click + Create new API key and give it a descriptive name (e.g. “CRM integration” or “Outbound calls”).
  3. Copy the secret key immediately and store it in your password manager, secrets store, or integration config.

The full API key is only shown once at creation. After you leave the page, you cannot view it again. If you lose it, create a new key and update your integration.

You can create up to 10 API keys per organization. The same key works across supported APIs unless you choose to rotate or separate keys by integration.See API Keys for limits, deletion, and security practices.

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.

We will add more APIs over time. Each will use the same x-api-key authentication unless noted otherwise on its reference page.

API feedback

Looking for an endpoint or integration we do not offer yet? Email us at help@replify.ai with API feedback in the subject line (or mention APIs in the message). Tell us what you are trying to build — we use customer input to prioritize what we ship next.