ContentBot Zapier API

Introduction

The ContentBot Zapier API was developed for the sole purpose of connecting your ContentBot account with Zapier. Although you can make direct requests to this API, we highly recommend using our Zapier App instead as it simplifies usage.

The have used a REST based architecture, meaning that pathing should be intuitive and easy to understand. All data is returned as JSON with the appropriate HTTP status code depending on the output produced.

Our API accepts both GET and POST methods, depending on the desired outcome of the path. All requests require an API key, please see the authentication section for more information.

Authentication

All requests require an API key, which can be obtained from within your ContentBot.ai account. Your API key should be appended to every request as a query paramater, as seen in the sample card on the right-hand side of the screen.

Before running any additional requests, you should call the /auth endpoint, as this will link your account. If this is not enabled at least once, no data will be pulled/pushed via the API.

Errors

We use standard HTTP response codes to indicate success or errors within the API. Codes within 2xx range indicate success, whereas codes within the 4xx range indicate a failure.

When an error occurs, for example a 401 (Unauthorized) status, you will still receive a response, however, it will be empty. As a result, you must evaluate the status code to determine if the request was successfult (200).

/auth

Authorize your ContentBot for the first time, and enable the Zapier integration. This will allow you to publish a document to Zapier.