| Enum Value | Description |
|---|---|
| 0 | Paused |
| 1 | Active |
| -1 | Banned |
| -2 | Spam Folder Unknown |
| -3 | Permanent Suspension |
The entire API V2 documentation is interactive and can be tested here. To the right side of every endpoint you will see a box with an example request. You can click on the "Try it" button to send a request to the server right from the docs. You will need to provide an API key by clicking the ApiKeyAuth_token blue text.
https://api.instantly.ai/
https://developer.instantly.ai/_mock/api/v2/
https://api.instantly.ai/api/v2/accounts/{email}
https://developer.instantly.ai/_mock/api/v2/api/v2/accounts/{email}
curl -i -X DELETE \
https://api.instantly.ai/api/v2/accounts/jon@doe.com \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json'The deleted Account
Timestamp when the account was created
Timestamp when the account was last updated
Organization ID that owns this account
Current warmup status of the account
| Enum Value | Description |
|---|---|
| 0 | Paused |
| 1 | Active |
| -1 | Banned |
| -2 | Spam Folder Unknown |
| -3 | Permanent Suspension |
Provider code for the account. Please make sure to specify the right provider code, otherwise your account will not work.
| Enum Value | Description |
|---|---|
| 1 | Custom IMAP/SMTP |
| 2 | |
| 3 | Microsoft |
| 4 | AWS |
User ID who added the account
User ID who last modified the account
Current status of the account
| Enum Value | Description |
|---|---|
| 1 | Active |
| 2 | Paused |
| -1 | Connection Error |
| -2 | Soft Bounce Error |
| -3 | Sending Error |
Timestamp when the account was last used
Timestamp when warmup was started
ID of the warmup pool this account belongs to
The gap between emails sent from this account in minutes (minimum wait time when used with multiple campaigns)
{ "email": "user@example.com", "timestamp_created": "2026-01-30T09:25:22.972Z", "timestamp_updated": "2026-01-30T09:25:22.972Z", "first_name": "John", "last_name": "Doe", "warmup": { "limit": 100, "advanced": { … }, "warmup_custom_ftag": "warmup", "increment": "disabled", "reply_rate": 0.1 }, "added_by": "019c0e38-b39c-7b67-94b2-a5cb91db010b", "daily_limit": 100, "modified_by": "019c0e38-b39c-7b67-94b2-a5cc696dca7a", "tracking_domain_name": "example.com", "tracking_domain_status": "active", "status": 1, "enable_slow_ramp": false, "inbox_placement_test_limit": 10, "organization": "019c0e38-b39c-7b67-94b2-a5cddf1d84eb", "timestamp_last_used": "2026-01-30T09:25:22.972Z", "warmup_status": 1, "status_message": { "code": "EENVELOPE", "command": "DATA", "response": "550-5.4.5 Daily user sending limit exceeded. For more information on Gmai", "e_message": "error: data command failed: 550-5.4.5 daily user sending limit exceeded", "responseCode": 550 }, "timestamp_warmup_start": "2026-01-30T09:25:22.972Z", "provider_code": 2, "setup_pending": false, "warmup_pool_id": "019c0e38-b39c-7b67-94b2-a5cee735b144", "is_managed_account": false, "dfy_password_changed": false, "stat_warmup_score": 85, "sending_gap": 10, "signature": "Best regards, John Doe" }
List of emails to enable warmup accounts for. The emails should be attached to accounts in your workspace.
List of emails to exclude when include_all_emails is true.
Optional filter to apply when include_all_emails is true. Can contain tag_id or other filter criteria.
https://api.instantly.ai/api/v2/accounts/warmup/enable
https://developer.instantly.ai/_mock/api/v2/api/v2/accounts/warmup/enable
curl -i -X POST \
https://api.instantly.ai/api/v2/accounts/warmup/enable \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{}'The requested Background Job
Unique identifier for the background job
Workspace ID
Type of background job
| Enum Value | Description |
|---|---|
| move-leads | Move Leads |
| import-leads | Import Leads |
| export-leads | Export Leads |
| update-warmup-accounts | Update Warmup Accounts |
| rename-variable | Rename Variable |
Job status
| Enum Value | Description |
|---|---|
| pending | The background job is waiting in the queue to be processed |
| in-progress | The background job is being processed |
| success | The background job has been successfully processed |
| failed | The background job has failed |
The id of the user that triggered the action that created the job
The id of the entity that the job is related to
Type of entity
| Enum Value | Description |
|---|---|
| list | The entity is a lead list |
| campaign | The entity is a campaign |
| workspace | The entity is a workspace |
{ "id": "675266e304a8e55b17f0228b", "workspace_id": "019c0e38-b397-79a1-9d91-60d94427121c", "user_id": "019c0e38-b397-79a1-9d91-60dac504c576", "type": "move-leads", "entity_id": "019c0e38-b397-79a1-9d91-60db586642a5", "entity_type": "list", "data": {}, "progress": 0, "status": "pending", "created_at": "2026-01-30T09:25:22.967Z", "updated_at": "2026-01-30T09:25:22.967Z" }
List of emails to disable warmup accounts for. The emails should be attached to accounts in your workspace.
List of emails to exclude when include_all_emails is true.
Optional filter to apply when include_all_emails is true. Can contain tag_id or other filter criteria.
https://api.instantly.ai/api/v2/accounts/warmup/disable
https://developer.instantly.ai/_mock/api/v2/api/v2/accounts/warmup/disable
curl -i -X POST \
https://api.instantly.ai/api/v2/accounts/warmup/disable \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{}'The requested Background Job
Unique identifier for the background job
Workspace ID
Type of background job
| Enum Value | Description |
|---|---|
| move-leads | Move Leads |
| import-leads | Import Leads |
| export-leads | Export Leads |
| update-warmup-accounts | Update Warmup Accounts |
| rename-variable | Rename Variable |
Job status
| Enum Value | Description |
|---|---|
| pending | The background job is waiting in the queue to be processed |
| in-progress | The background job is being processed |
| success | The background job has been successfully processed |
| failed | The background job has failed |
The id of the user that triggered the action that created the job
The id of the entity that the job is related to
Type of entity
| Enum Value | Description |
|---|---|
| list | The entity is a lead list |
| campaign | The entity is a campaign |
| workspace | The entity is a workspace |
{ "id": "675266e304a8e55b17f0228b", "workspace_id": "019c0e38-b397-79a1-9d91-60d94427121c", "user_id": "019c0e38-b397-79a1-9d91-60dac504c576", "type": "move-leads", "entity_id": "019c0e38-b397-79a1-9d91-60db586642a5", "entity_type": "list", "data": {}, "progress": 0, "status": "pending", "created_at": "2026-01-30T09:25:22.967Z", "updated_at": "2026-01-30T09:25:22.967Z" }
This entity represents a tag being assigned to a specific campaign or email account. When an email account is assigned a tag, a new custom tag mapping entry is created, which connects the tag (tag_id field) with the email account (resource_id field). You can use it to see which tag si connected to which resource.