Bison API Support Guideline

To help us investigate and resolve your API issue as quickly as possible, please include the following details in your request:

1. Your Bison Instance URL:

   Please provide the full URL of the Bison instance you are working with (e.g., https://yourcompany.emailbison.com). This ensures we can pinpoint the correct environment.

2. Workspace Name

   Specify the exact name of the workspace where the issue is occurring. This helps us locate the correct context for your API call.

3. API Endpoint Being Called

   Include the full API endpoint you're trying to access (e.g., /api/leads, /api/bounce, etc.).

4. HTTP Method Used

   Let us know which HTTP method you're using to make the request (Examples below):

   • GET

   • POST

   • PUT

   • PATCH

   • DELETE

5. Request Body or Full URL (with Query Parameters)
   Depending on the request type, please include either:

   • The full JSON body of your request (for POST, PUT, etc.)

   • Or the full endpoint URL with query parameters (for GET requests)

   This allows us to reproduce and inspect the exact call you're making.

6. Full API Response

   Copy and paste the complete response you received from the API, including the status code and any error messages. This helps us understand how the server handled your request.

7. Description of the Issue

   Briefly explain what you expected to happen and what actually happened. Be specific about what is not working as intended.

   The more complete and detailed your submission is, the faster we can assist you.

Fastest way to get support

If you want the fastest support, please submit a cURL request with complete request data (including your API token) to the support rep.

You can do this by passing the request thorough an HTTP testing tool like Postman

Here is a guide: https://www.loom.com/share/cd238081d25a40fa92d7916253b1ca24?sid=2897529a-5df6-427b-9901-6d2c489997d9

Do you have a specific issue with a no-code tool like Zapier, n8n, or make.com?]

Our goal is to ensure that our API is working correctly. Every no-code tool will have their own nuances to how they process API requests.

Most of them are going to be user errors.

We recommend going through our community support for specific issues that are no-code specific.

Once we validate that the API requests and responses are working correctly, we’re unable to dig into every no-code workflow unfortunately.