What are SendFox's API Endpoints?

SendFox API endpoints reference: the base URL, authentication, and the most-used endpoints for managing contacts, lists, and campaigns over the REST API.

Before you start

  • Base URL: all endpoints build from https://api.sendfox.com.
  • Authentication: send a personal access token in the Authorization: Bearer header—see how to get access tokens.
  • Plan requirement: the API is included with paid plans. On the Free plan every endpoint returns HTTP 402 with "API access requires a paid plan."
  • Full reference: this article covers the most-used endpoints; the complete, always-current reference (including forms, automations, custom contact fields, and domains) is at sendfox.com/developer/docs.

User

GET /me

Gets information for the authenticated user.

Lists

GET /lists

Gets paginated contact lists.

GET /lists/{list_id}

Gets a list by ID.

POST /lists

Creates a new list.

Parameter    
name required The name of the list.

DELETE /lists/{list_id}/contacts/{contact_id}

Removes a contact from a list.

Parameter    
list_id required ID of the list.
contact_id required ID of the contact.

Contacts

GET /contacts

Gets paginated contacts.

GET /contacts/{contact_id}

Gets a contact by ID.

GET /contacts?email={contact_email}

Gets a contact by email address.

POST /contacts

Creates a new contact.

Parameter    
email required Contact email address.
first_name optional Contact first name.
last_name optional Contact last name.
lists optional Array of list IDs to add the contact to, e.g. lists[]=123&lists[]=456

PATCH /unsubscribe

Unsubscribes a contact.

Parameter    
email required The email of the contact.

Campaigns

GET /campaigns

Gets paginated campaigns.

GET /campaigns/{campaign_id}

Gets a campaign by ID.

Response codes

API responses use standard HTTP response codes (see the MDN reference) with JSON bodies:

  • 2xx (200–299) indicate success.
  • 4xx (400–499) indicate validation or authorization errors—a message is generally provided with details.
  • 5xx (500–599) indicate a server error on our end.

Troubleshooting

HTTP 402: "API access requires a paid plan."

  • The API is locked on the Free plan. Upgrade to the Lifetime or a Pro plan to use it.

HTTP 401 Unauthorized

  • Your token is missing, revoked, or malformed. Create a fresh one—see getting access tokens—and send it as Authorization: Bearer <token>.
  • Still stuck? Visit the SendFox Help Center at help.sendfox.com.

Frequently Asked Questions

Are there more endpoints than these?

Yes—forms, automations, custom contact fields, domains, campaign stats, batch contact imports, and more. The complete reference is at sendfox.com/developer/docs.

How do I make my first request?

Follow the step-by-step Postman walkthrough in how to create API requests.

Can I use the API on the Free plan?

No—every endpoint returns HTTP 402 on the Free plan. API access is included with paid plans.

Still need help? Contact Us Contact Us