Introduction
Authentication
Welcome to the Reply.io API guide. Let’s get you integrated smoothly!
API Endpoint
Our platform utilizes the endpoint: api.reply.io. We offer two versions of our API: V1 and V2, each with its unique functionalities. You’re free to employ both versions in tandem if desired.
Authentication
- Log in to your Reply account.
- Navigate to Settings → API Keys.
- Choose the appropriate key type and copy its value.
Key Types & Access Levels
| Key Type | Example Prefix | Scope | Typical Use |
|---|---|---|---|
| User | usr_xxx | A single user’s data & actions | Personal scripts and one‑off integrations |
| Team | team_xxx | All members within a single team | Shared dashboards, team automations |
| Organization | org_xxx | Entire organization across all teams | Company‑wide BI, system‑level integrations |
Note: API rate limits are tracked per key. Separate keys help teams monitor usage independently.
Constructing API Requests
All your requests will start with either:
https://api.reply.io/v1/https://api.reply.io/v2/
Response Codes
200– All good! Request was successful.201– Success! A new item was created.400– Uh‑oh! There’s an issue with your input parameter. Check the response for more information.401– User not found. No users match the API key provided.403– Access denied. The API key doesn’t have the required permissions for the resource.404– Resource not found. Double‑check your URL or identifier. More details can be found in the response.500– Our bad! Internal server error. We’ve been notified and will get on it ASAP.
Rate Limits
To ensure optimal performance and equitable usage for all users, the Reply API enforces:
- Monthly API Calls: Up to 15,000 calls per key per month.
- API Throttling: No general throttling, but certain requests may be subject to throttling. Refer to the specific request documentation for details.