version: "1.0.0"

EmailBison API — Complete Documentation

Source: https://docs.emailbison.com + https://dedi.emailbison.com/api/reference API Version: v1.0.0 (OAS 3.0.3) Base URL: https://dedi.emailbison.com (or your custom instance URL) Scraped: 2026-04-10

Example Instance — Quick Reference

Merge Tags (Email Bison Syntax)

Email Bison uses single curly braces + UPPERCASE for all variables:

NOT the same as SmartLead. SmartLead uses {{first_name}} (double curly, lowercase). Email Bison uses {FIRST_NAME} (single curly, uppercase). Do not mix them.

Campaign Naming Convention (Client Standard)

QFY | ProgramType | Channel | CampaignType | CampaignName

Examples:

• Q2FY26 | Targeted Events | Email | Launch | Portland WTS Dinner 5/6
• Q2FY26 | Brand Campaign | Email | Pre-Launch | CMO Marketing Leadership

Standard Campaign Settings (example)

{
  "max_emails_per_day": 700,
  "max_new_leads_per_day": 700,
  "plain_text": true,
  "open_tracking": false,
  "can_unsubscribe": false
}

Standard Schedule (example)

{
  "monday": true, "tuesday": true, "wednesday": true,
  "thursday": true, "friday": true, "saturday": false, "sunday": false,
  "start_time": "09:00", "end_time": "18:00",
  "timezone": "America/New_York"
}

CSV Bulk Upload Column Mapping

Use flat key mapping (NOT array indexed):

curl 'https://send.example-mail.com/api/leads/bulk/csv' \
  --request POST \
  --header 'Authorization: Bearer 2|5KmZhWXg08i0OjsHgSSeC0WtEFEvIGDGODpC0KbN9b6d783f' \
  --form 'name=Lead List Name' \
  --form 'csv=@/path/to/file.csv' \
  --form 'columnsToMap[first_name]=First Name' \
  --form 'columnsToMap[last_name]=Last Name' \
  --form 'columnsToMap[email]=Email' \
  --form 'columnsToMap[company]=Company' \
  --form 'columnsToMap[title]=Title'

Gotchas (Learned from Usage)

• wait_in_days minimum is 1 (not 0) — even for the first step
• CSV column mapping uses columnsToMap[field_name]=CSV Header format (NOT columnsToMap[0][field_name])
• Apostrophes in email body: use Python json.dumps() to build the payload safely — shell quoting breaks JSON
• Lead list upload is async — status starts as "Unprocessed", leads sync within ~5 minutes
• Attaching leads to an active campaign takes up to 5 minutes to sync

Table of Contents

1. Authentication
2. Pagination
3. Terminology & Parameters
4. Workspaces
5. Account Management
6. Email Accounts (Sender Emails)
7. Campaigns
8. Campaign Sequences
9. Campaign Schedule
10. Leads
11. Custom Variables
12. Tags
13. Master Inbox / Replies
14. Webhooks
15. Email & Domain Blocklist
16. Custom Tracking Domains
17. Campaign Events / Analytics
18. Warmup
19. Reply Templates
20. Scheduled Emails
21. Clay Integration
22. Bulk Uploader Tool
23. Walkthroughs

Authentication

EmailBison uses Bearer tokens for all API requests.

Token Types

Creating Tokens

• UI: Settings -> Developer API -> New API Token
• API: POST /api/workspaces/v1.1/{team_id}/api-tokens (requires super-admin key)
• Body: { "name": "token name" }

Authorization Header

All requests must include:

Authorization: Bearer YOUR_API_KEY

Example:

curl https://dedi.emailbison.com/api/users \
  --header 'Authorization: Bearer 9|q8kSmhjJRqJVT2kc1M0ezX640Pxk'

Pagination

Paginated responses return 15 entries per page. Response structure:

{
    "data": [...],
    "links": {
        "first": "https://dedi.emailbison.com/api/leads?page=1",
        "last": "https://dedi.emailbison.com/api/leads?page=4",
        "prev": null,
        "next": "https://dedi.emailbison.com/api/leads?page=2"
    },
    "meta": {
        "current_page": 1,
        "from": 1,
        "last_page": 4
    }
}

Retrieving pages: Append ?page={page_number} to any paginated endpoint.

Programmatic pagination: Loop requests, incrementing page number until meta.last_page is reached, or follow links.next until it is null.

Terminology & Parameters

Base URL

Each EmailBison instance has its own base URL (the same URL you log in at). Example: https://send.greenmarketing.com. All endpoint paths are relative to this.

Parameter Types

Query parameter arrays: Use bracket syntax: ?tag_ids[]=1&tag_ids[]=2&tag_ids[]=3

Body parameters can be sent as query parameters if the parameter names match (EmailBison auto-converts).

Workspaces

Workspaces separate workflows into isolated environments. One workspace per client is recommended.

Scope: Every record (leads, tags, custom variables, campaigns) is unique per workspace and has its own ID. Exception: Sender emails can only exist in one workspace at a time.

Endpoints (v1.1)

Create Workspace

curl https://dedi.emailbison.com/api/workspaces/v1.1 \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{ "name": "New Workspace" }'

Create User

curl https://dedi.emailbison.com/api/workspaces/v1.1/users \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{
  "name": "John Doe",
  "password": "securepassword",
  "email": "example@example.com",
  "role": "admin"
}'

Roles: admin, editor, client

Invite & Accept Members

# Invite
curl https://dedi.emailbison.com/api/workspaces/v1.1/invite-members \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{ "email": "user@example.com", "role": "admin" }'
 
# Accept (use team_invitation_id from invite response)
curl https://dedi.emailbison.com/api/workspaces/v1.1/accept/{team_invitation_id} \
  --request POST \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN'

Account Management

User Details Response

{
  "data": {
    "id": 1,
    "name": "John Doe",
    "email": "john@doe.com",
    "team": {
      "id": 1,
      "name": "John Doe's Team",
      "personal_team": true,
      "main": true,
      "parent_id": null,
      "sender_email_limit": 100000,
      "warmup_limit": 100000,
      "has_access_to_warmup": false,
      "has_access_to_healthcheck": false,
      "total_email_verification_credits": 0,
      "remaining_email_verification_credits": 0
    },
    "profile_photo_url": "https://ui-avatars.com/api/?name=J&color=7F9CF5&background=EBF4FF"
  }
}

Headless UI Token

Generate a token for embedded email account connection:

curl https://dedi.emailbison.com/api/users/headless-ui-token \
  --request POST \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN'

Use the token in an iframe: https://your-bison-url.com/headless-ui-login?token=YOUR_HEADLESS_UI_TOKEN

Note: Requesting URL must be whitelisted first.

Email Accounts (Sender Emails)

Sender emails are the accounts EmailBison sends from. Unlimited storage. Three types: Google, Microsoft, Custom SMTP. Sender emails can only exist in one workspace at a time.

Endpoints

Add Custom SMTP Accounts (CSV)

curl https://dedi.emailbison.com/api/sender-emails/imap-smtp \
  --request POST \
  --header 'Content-Type: multipart/form-data' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --form 'csv=@/path/to/accounts.csv'

Bulk Add Sender Emails

curl https://dedi.emailbison.com/api/sender-emails/bulk \
  --request POST \
  --header 'Content-Type: multipart/form-data' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --form 'csv=@/path/to/accounts.csv'

Campaigns

Campaigns orchestrate emails: what gets sent, to whom, and when.

Key behaviors:

• Smart scheduling: random send pattern within your sending window to avoid automation detection
• ESP Matching: unopinionated — EmailBison tags leads with their ESP, you decide matching strategy
• Lead-sender affinity: once a lead gets an email from a sender, that sender handles all remaining steps + followup campaigns
• Campaign scheduler runs on resume and at end of each sending day

Campaign Endpoints

Campaign Settings

Update via PATCH /api/campaigns/{id}/update:

curl 'https://dedi.emailbison.com/api/campaigns/{id}/update' \
  --request PATCH \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{
  "max_emails_per_day": 500,
  "max_new_leads_per_day": 100,
  "plain_text": true,
  "open_tracking": true,
  "can_unsubscribe": true,
  "unsubscribe_text": "Click here to unsubscribe"
}'

Adding Leads to Campaign

Note: Adding leads to an active campaign takes up to 5 minutes to sync.

# Attach by lead list
curl 'https://dedi.emailbison.com/api/campaigns/6/leads/attach-lead-list' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{ "lead_list_id": 1 }'
 
# Attach by lead IDs
curl 'https://dedi.emailbison.com/api/campaigns/6/leads/attach-leads' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{ "lead_ids": [1, 2, 3] }'

Adding/Removing Sender Emails to Campaign

# Attach
POST /api/campaigns/{campaign_id}/attach-sender-emails
Body: { "sender_email_ids": [1, 2, 3] }
 
# Remove
DELETE /api/campaigns/{campaign_id}/remove-sender-emails
Body: { "sender_email_ids": [1, 2, 3] }

Campaign Sequences

Sequences are the email steps sent in a campaign.

Endpoints

v1.1 Sequence Endpoints (newer)

Sequence Step Fields

Create Sequence Example

curl 'https://dedi.emailbison.com/api/campaigns/{campaign_id}/sequence-steps' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{
    "title": "Initial outreach",
    "sequence_steps": [
        {
            "email_subject": "Hey {FIRST_NAME}",
            "order": 1,
            "email_body": "You should check this out!",
            "wait_in_days": 3,
            "thread_reply": false
        },
        {
            "email_subject": "Following up",
            "order": 2,
            "email_body": "Just checking in...",
            "wait_in_days": 3,
            "thread_reply": true
        }
    ]
}'

Campaign Schedule

Endpoints

Schedule Fields

Create Schedule Example

curl 'https://dedi.emailbison.com/api/campaigns/{campaign_id}/schedule' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{
  "monday": true, "tuesday": true, "wednesday": true,
  "thursday": true, "friday": true, "saturday": false, "sunday": false,
  "start_time": "09:00", "end_time": "17:00",
  "timezone": "America/New_York",
  "save_as_template": false
}'

Common Timezone Strings

Leads

Leads (contacts) are email addresses targeted by campaigns. Unlimited storage. CSVs and campaigns limited to 50,000 leads at once.

Key behaviors:

• Same lead (email) can exist in multiple workspaces (separate IDs)
• Updating a CSV with same emails updates leads in-place (including in active campaigns)
• Every lead auto-tagged with their ESP (for ESP matching)

Endpoints

Create Single Lead

Required fields: first_name, last_name, email Optional fields: title, company, notes, custom_variables

curl https://dedi.emailbison.com/api/leads \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{
  "first_name": "John",
  "last_name": "Doe",
  "email": "john@doe.com",
  "title": "Engineer",
  "company": "Acme Corp",
  "notes": "Important client",
  "custom_variables": [
    { "name": "phone number", "value": "9059999999" }
  ]
}'

Bulk Upload Leads (CSV)

50,000 lead limit per CSV file. Do NOT set Content-Type header (auto-set to multipart/form-data).

curl https://dedi.emailbison.com/api/leads/bulk/csv \
  --request POST \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --form 'name=My Lead List' \
  --form 'csv=@/path/to/list.csv' \
  --form 'columnsToMap[0][first_name]=name' \
  --form 'columnsToMap[0][last_name]=last name' \
  --form 'columnsToMap[0][email]=email' \
  --form 'columnsToMap[0][company]=company name'

Custom Variables

Custom variables attach arbitrary data to leads. Unique per workspace — must be created before attaching to leads.

Endpoints

Attaching to Leads

When creating or updating a lead, pass custom_variables as an array:

{
  "first_name": "John",
  "last_name": "Doe",
  "email": "john@doe.com",
  "custom_variables": [
    { "name": "phone_number", "value": "123-456-7890" },
    { "name": "linkedin_url", "value": "https://linkedin.com/in/johndoe" }
  ]
}

Using Variables in Email Copy

Reference variables in email subjects/bodies with uppercase curly brace syntax:

Hey {FIRST_NAME}, I noticed {COMPANY} is growing...

Variables must exist as custom variables in the workspace.

Tags

Tags organize leads, campaigns, and sender emails. Unique per workspace. Emit webhooks on attach/remove.

Default Tags (auto-created per workspace)

Interested, Meeting Booked, Google, Outlook, Zoho, Custom Mail Server, Proofpoint, Mimecast, Barracuda, Automated Reply

Endpoints

Create Tag

curl https://dedi.emailbison.com/api/tags \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{ "name": "Important", "default": false }'

Attach/Remove Tags

Body requires tag_ids array + one of lead_ids, campaign_ids, or sender_email_ids:

# Attach tags 1,2 to sender emails 3,4
curl https://dedi.emailbison.com/api/tags/attach-to-sender-emails \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{ "tag_ids": [1, 2], "sender_email_ids": [3, 4] }'
 
# Remove tags (same body format, same endpoints, use POST for remove-from-*)

Master Inbox / Replies

The Master Inbox is a unified view into all sender email accounts in a workspace.

Filtering: By campaigns, reply statuses, sender emails, lead tags. Smart filter: Toggle Smart filter warmup emails from other providers in Settings -> Master Inbox. Add ignore phrases for remaining warmup emails.

Reply Endpoints

Fetching Replies for a Lead

GET /api/leads/{lead_id}/replies

Query parameters:

Getting Sent Emails for a Lead

GET /api/leads/{lead_id_or_email}/sent-emails

Responding to Messages

POST /api/replies/{reply_id}/reply

Attaching Leads to Untracked Replies

1. Get scheduled emails: GET /api/scheduled-emails/{lead_id_or_email}
2. Attach to reply: POST /api/replies/{reply_id}/attach-email-to-reply with body { "scheduled_email_id": 123 }

Webhooks

Webhooks send HTTP POST requests when events occur in your EmailBison instance.

Endpoints

Available Webhook Events

Testing Webhooks

Via UI: Settings -> Webhooks -> Edit -> Send test webhook Via API: POST /api/webhook-events/test-event

Email & Domain Blocklist

Email Blocklist

Domain Blocklist

Custom Tracking Domains

Campaign Events / Analytics

Drill down into campaign event stats by dates, campaign IDs, and/or sender email IDs.

Warmup

Manage warmup settings for email accounts.

Reply Templates

Manage templated responses for replying to leads.

Scheduled Emails

Ignore Phrases

Filter out warmup/noise emails from master inbox.

Clay Integration

EmailBison has an official Clay integration with native enrichments.

Setup

1. Create API key: Generate an api-user key in EmailBison (Settings -> Developer API)
2. Connect in Clay: Settings -> Connections -> + Add connection -> search EmailBison

• Connection name: workspace name
• Workspace domain (Instance URL): your EmailBison URL
• API Key: your api-user key

1. Each workspace needs its own connection

Native Enrichments

HTTP API Enrichment (for non-native requests)

GET requests: Use Clay's HTTP API enrichment with GET method, paste endpoint URL, add query parameters in Body section.

POST requests (e.g., creating leads):

1. Add HTTP API enrichment, select POST method
2. Authenticate via saved account or Authorization header
3. Map Clay columns to JSON body fields using / to reference columns
4. For custom fields, use custom_variables array
5. To attach leads to campaigns, chain a second HTTP API enrichment using the lead ID returned from step 1

Bulk Uploader Tool

Native desktop tool for bulk uploading Microsoft accounts. Available for Windows, macOS, Linux.

Download:

• Windows: https://dedi.emailbison.com/microsoft-uploader/emailbison_uploader_windows.zip
• macOS: https://dedi.emailbison.com/microsoft-uploader/emailbison_uploader_mac.zip
• Linux: https://dedi.emailbison.com/microsoft-uploader/emailbison_uploader_linux.zip

Key Flags

CSV Format

Headers: name, email, password Optional column: use_as_admin (for admin consent prompt)

Admin Consent Fix

For "Need Admin Approval" errors: include one account per tenant with "Cloud Applications Admin" role, mark use_as_admin=true in CSV.

Walkthroughs

Creating Template Workspaces

Automate workspace creation with standard setup (users, tags, API tokens, webhooks):

1. POST /api/workspaces/v1.1 (create workspace, needs super-admin)
2. POST /api/workspaces/v1.1/{team_id}/api-tokens (create api-user key)
3. Switch to api-user key for remaining requests
4. POST /api/workspaces/v1.1/invite-members (for each user)
5. POST /api/workspaces/v1.1/accept/{team_invitation_id} (accept each)
6. POST /api/tags (for each tag)
7. POST /api/webhook-url (create webhook with desired events)

Slack Notification on Campaign Reply

1. Create webhook in EmailBison: Settings -> Webhooks -> New Webhook URL
2. Subscribe to Contact Replied event
3. Point webhook URL to your automation tool (n8n, Zapier, etc.)
4. Parse webhook payload and send Slack message

Complete Campaign Launch Workflow (API)

1. Create campaign: POST /api/campaigns with { "name": "..." }
2. Update settings: PATCH /api/campaigns/{id}/update (limits, tracking, etc.)
3. Create schedule: POST /api/campaigns/{id}/schedule (days, times, timezone)
4. Create sequence: POST /api/campaigns/{id}/sequence-steps (email steps)
5. Add sender emails: POST /api/campaigns/{id}/attach-sender-emails
6. Add leads: POST /api/campaigns/{id}/leads/attach-leads or attach-lead-list
7. Verify setup:

• GET /api/campaigns/{id} (settings)
• GET /api/campaigns/{id}/schedule (schedule)
• GET /api/campaigns/{id}/sequence-steps (sequences)

1. Launch: PATCH /api/campaigns/{id}/resume
2. Pause: PATCH /api/campaigns/{id}/pause

Full API Endpoint Index

Account Management (4)

• GET /api/users
• POST /api/users/profile-picture
• PUT /api/users/password
• POST /api/users/headless-ui-token

Campaigns (37)

• GET /api/campaigns
• POST /api/campaigns
• POST /api/campaigns/{id}/duplicate
• PATCH /api/campaigns/{id}/pause
• PATCH /api/campaigns/{id}/resume
• PATCH /api/campaigns/{id}/archive
• PATCH /api/campaigns/{id}/update
• POST /api/campaigns/{id}/schedule
• GET /api/campaigns/{id}/schedule
• PUT /api/campaigns/{id}/schedule
• GET /api/campaigns/schedule/templates
• GET /api/campaigns/schedule/available-timezones
• GET /api/campaigns/sending-schedules
• GET /api/campaigns/{id}/sending-schedule
• POST /api/campaigns/{id}/create-schedule-from-template
• GET /api/campaigns/{id}/sequence-steps
• POST /api/campaigns/{id}/sequence-steps
• PUT /api/campaigns/sequence-steps/{sequence_id}
• PATCH /api/campaigns/sequence-steps/{id}/activate-or-deactivate
• DELETE /api/campaigns/sequence-steps/{id}
• POST /api/campaigns/sequence-steps/{id}/test-email
• GET /api/campaigns/{id}/replies
• GET /api/campaigns/{id}/leads
• DELETE /api/campaigns/{id}/leads
• POST /api/campaigns/{id}/leads/attach-lead-list
• POST /api/campaigns/{id}/leads/attach-leads
• POST /api/campaigns/{id}/leads/stop-future-emails
• GET /api/campaigns/{id}/scheduled-emails
• GET /api/campaigns/{id}/sender-emails
• POST /api/campaigns/{id}/stats
• POST /api/campaigns/{id}/attach-sender-emails
• DELETE /api/campaigns/{id}/remove-sender-emails
• POST /api/campaigns/{id}/leads/move-to-another-campaign
• GET /api/campaigns/{id}/line-area-chart-stats
• GET /api/campaigns/{id}
• DELETE /api/campaigns/bulk
• DELETE /api/campaigns/{id}

Campaigns v1.1 (3)

• GET /api/campaigns/v1.1/{id}/sequence-steps
• POST /api/campaigns/v1.1/{id}/sequence-steps
• PUT /api/campaigns/v1.1/sequence-steps/{sequence_id}

Replies (14)

• GET /api/replies
• GET /api/replies/{id}
• POST /api/replies/new
• POST /api/replies/{reply_id}/reply
• POST /api/replies/{reply_id}/forward
• PATCH /api/replies/{reply_id}/mark-as-interested
• PATCH /api/replies/{reply_id}/mark-as-not-interested
• PATCH /api/replies/{reply_id}/mark-as-read-or-unread
• PATCH /api/replies/{reply_id}/mark-as-automated-or-not-automated
• PATCH /api/replies/{reply_id}/unsubscribe
• DELETE /api/replies/{reply_id}
• GET /api/replies/{reply_id}/conversation-thread
• POST /api/replies/{reply_id}/attach-scheduled-email-to-reply
• POST /api/replies/{reply_id}/followup-campaign/push

Email Accounts (13)

• GET /api/sender-emails
• GET /api/sender-emails/{id}/campaigns
• GET /api/sender-emails/{id}
• PATCH /api/sender-emails/{id}
• DELETE /api/sender-emails/{id}
• GET /api/sender-emails/{id}/replies
• GET /api/sender-emails/{id}/oauth-access-token
• PATCH /api/sender-emails/signatures/bulk
• PATCH /api/sender-emails/daily-limits/bulk
• POST /api/sender-emails/imap-smtp
• POST /api/sender-emails/bulk
• POST /api/sender-emails/{id}/check-mx-records
• POST /api/sender-emails/bulk-check-missing-mx-records

Email Blacklist (5)

• GET /api/blacklisted-emails
• POST /api/blacklisted-emails
• GET /api/blacklisted-emails/{id}
• DELETE /api/blacklisted-emails/{id}
• POST /api/blacklisted-emails/bulk

Domain Blacklist (5)

• GET /api/blacklisted-domains
• POST /api/blacklisted-domains
• GET /api/blacklisted-domains/{id}
• DELETE /api/blacklisted-domains/{id}
• POST /api/blacklisted-domains/bulk

Tags (10)

• GET /api/tags
• POST /api/tags
• GET /api/tags/{id}
• DELETE /api/tags/{tag_id}
• POST /api/tags/attach-to-campaigns
• POST /api/tags/remove-from-campaigns
• POST /api/tags/attach-to-leads
• POST /api/tags/remove-from-leads
• POST /api/tags/attach-to-sender-emails
• POST /api/tags/remove-from-sender-emails

Custom Tracking Domains (4)

• GET /api/custom-tracking-domain
• POST /api/custom-tracking-domain
• GET /api/custom-tracking-domain/{id}
• DELETE /api/custom-tracking-domain/{id}

Webhooks (5)

• GET /api/webhook-url
• POST /api/webhook-url
• GET /api/webhook-url/{id}
• PUT /api/webhook-url/{id}
• DELETE /api/webhook-url/{id}

Webhook Events (3)

• GET /api/webhook-events/sample-payload
• GET /api/webhook-events/event-types
• POST /api/webhook-events/test-event

Campaign Events (1)

• GET /api/campaign-events/stats

Custom Lead Variables (2)

• GET /api/custom-variables
• POST /api/custom-variables

Ignore Phrases (4)

• GET /api/ignore-phrases
• POST /api/ignore-phrases
• GET /api/ignore-phrases/{id}
• DELETE /api/ignore-phrases/{id}

Leads (17)

• GET /api/leads
• POST /api/leads
• GET /api/leads/{lead_id}
• PUT /api/leads/{lead_id}
• PATCH /api/leads/{lead_id}
• DELETE /api/leads/{lead_id}
• GET /api/leads/{lead_id}/replies
• POST /api/leads/multiple
• POST /api/leads/create-or-update/multiple
• POST /api/leads/create-or-update/{lead_id}
• PATCH /api/leads/{lead_id}/unsubscribe
• POST /api/leads/{lead_id}/blacklist
• POST /api/leads/bulk/csv
• GET /api/leads/{lead_id}/scheduled-emails
• GET /api/leads/{lead_id}/sent-emails
• PATCH /api/leads/{lead_id}/update-status
• PATCH /api/leads/bulk-update-status
• DELETE /api/leads/bulk

Reply Templates (5)

• GET /api/reply-templates
• POST /api/reply-templates
• GET /api/reply-templates/{id}
• PUT /api/reply-templates/{id}
• DELETE /api/reply-templates/{id}

Scheduled Emails (2)

• GET /api/scheduled-emails
• GET /api/scheduled-emails/{id}

Warmup (5)

• GET /api/warmup/sender-emails
• PATCH /api/warmup/sender-emails/enable
• PATCH /api/warmup/sender-emails/disable
• PATCH /api/warmup/sender-emails/update-daily-warmup-limits
• GET /api/warmup/sender-emails/{id}

Workspaces v1.1 (15)

• GET /api/workspaces/v1.1
• POST /api/workspaces/v1.1
• POST /api/workspaces/v1.1/users
• POST /api/workspaces/v1.1/{team_id}/api-tokens
• POST /api/workspaces/v1.1/switch-workspace
• DELETE /api/workspaces/v1.1/{team_id}
• PUT /api/workspaces/v1.1/{team_id}
• GET /api/workspaces/v1.1/{team_id}
• POST /api/workspaces/v1.1/invite-members
• POST /api/workspaces/v1.1/accept/{team_invitation_id}
• DELETE /api/workspaces/v1.1/members/{user_id}
• GET /api/workspaces/v1.1/master-inbox-settings
• PATCH /api/workspaces/v1.1/master-inbox-settings
• GET /api/workspaces/v1.1/stats
• GET /api/workspaces/v1.1/line-area-chart-stats

Total: ~150+ endpoints across 17 API groups

_Part of Frontal — free, open GTM skills for your AI agent. Browse the library →_