> ## 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.

# Overview

> Authentication, API keys, and available Replify APIs

export const ContactEmail = () => {
  return <a href="mailto:help@replify.ai">help@replify.ai</a>;
};

export const BaseUrl = ({path = '', children}) => {
  const baseUrl = 'https://app.replify.ai';
  const fullUrl = path ? `${baseUrl}${path.startsWith('/') ? path : `/${path}`}` : baseUrl;
  if (children) {
    return <a href={fullUrl}>{children}</a>;
  }
  return fullUrl;
};

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.

<Warning>
  **Plus plan required:** API keys and API access are available on the Plus plan.
</Warning>

## Authentication

All current Replify APIs use the same authentication model:

* Send your API key secret in the **`x-api-key`** header on every request.
* API Gateway validates the key and routes the request to your organization.

For endpoints that accept a JSON body, also send:

```http theme={null}
Content-Type: application/json
```

**Production base URL:** `https://api.heylibby.com/api/v1`

Individual API pages document paths, payloads, and responses. The [legacy Outbound Phone Calling API](/api-documentation/outbound-phone-calling-api-legacy) 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 <BaseUrl path="/settings/api-keys">API Key Management</BaseUrl> 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.

<Warning>
  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.
</Warning>

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](/integrations/api-keys) for limits, deletion, and security practices.

## Available APIs

<Note>
  **Migrating from the legacy outbound API?** If you use the [legacy Outbound Phone Calling API](/api-documentation/outbound-phone-calling-api-legacy), switch to the current API by **July 1, 2026**. Your account manager can help with endpoint and testing changes.
</Note>

<CardGroup cols={2}>
  <Card title="Outbound Phone Calling" icon="phone" href="/api-reference/outbound-calling/initiate-outbound-call">
    Schedule a single immediate outbound call for an assistant — testing, demos, or one-off dials.
  </Card>

  <Card title="Campaign Service" icon="users" href="/api-reference/campaigns/manage-campaign-contacts">
    Add, update, or remove contacts in campaigns programmatically.
  </Card>
</CardGroup>

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 <ContactEmail /> 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.