The Selz API is organized around REST. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which are understood by off-the-shelf HTTP clients.

Every response, including errors, returns JSON. We use OAuth2 for our API authorization.

The API documentation is generated programmatically, meaning that the API docs are kept accurate and up to date. Everything that can be done via the API will be reflected in the documentation.

To find out which properties and values can be included when making a POST, PUT, GET, or UPDATE call on an object via the API, check the API Reference. There are examples reflecting all possible ways to interact with that object.


For reference of the payloads and endpoints, head over to the API reference.


All API requests are made to and all requests are served over HTTPS. The current version is v1.


All responses, including errors, return JSON. Also our POST and PUT requests require a JSON object for the body. There are more specific examples provided in the Resources.

    "id": "526087bd316c9af61145dd87",
    "first_name": "John",
    "last_name": "Doe",
    "email": "",
    "company": "Selz Inc"


At present v1 is the current and only version for Selz API.

Date format

All dates in the API use UTC and are strings in the ISO 8601 "combined date and time representation" format:


Rate Limiting

Requests are limited to 200 requests per minute per account. All API keys associated with the same account count against the minute rate limit. Response code 429 is returned when the throttle limit has been reached. A "Retry-After" header is returned indicating how many seconds to wait until retry. Applicable to all requests