API Docs
  • Overview
  • Authentication
  • Errors
  • Error codes
  • Expanding Responses
  • API Reference
    • Contacts
      • The contact object
      • List all contacts
      • Total contacts
      • Retrieve a contact
      • Create a contact
      • Update a contact
      • Delete a contact
      • Bulk delete contacts
Con tecnología de GitBook
En esta página
  • Content API Basics
  • Example Requests
  • gzip
  • Input/Output Format
  • CORS
  • Pagination
  • Request IDs
  • Getting Help

¿Te fue útil?

Overview

SiguienteAuthentication

Última actualización hace 3 años

¿Te fue útil?

Content API Basics

The Treevox Content API gives you access to the content management features you see in our web app and lets you extend them for use in your own app. It strives to be and is organized around the main resources you’re familiar with from the Treevox web interface.

Before you do anything, you should create a account that you can test the API against and register for an so that you can make API calls.

Example Requests

Sample API calls are provided next to each method using , a standard command line tool. All you need to do is drop in your specific parameters, and you can test the calls from the command line. If the command line isn’t your preference, a great alternative is , an easy-to-use.

gzip

If you would like responses from Treevox to be compressed for faster response times, simply include an Accept-Encoding header with a value of gzip, deflate , and responses will be .

Input/Output Format

Both request body data and response data are formatted as .

CORS

, or cross-origin resource sharing, is a mechanism that allows a web page to make XMLHttpRequests to another domain (i.e. a domain different from the one it was loaded from). CORS is supported in a . The Treevox API supports CORS.

Pagination

Endpoints that return arrays support limit and offset as URL parameters. Limit defines the maximum number of records that will be returned on a page. The number of records is not guaranteed to be the number specified as visibility rules may filter out items. To avoid duplicates being returned we recommend the following logic:

  • To retrieve the next page, set offset=offset+limit

  • If total count from previous response is >= the new offset, you are done, no need to ask for another page

Note that offset is zero based, defaults for limit vary by endpoint.

Request IDs

Getting Help

To get in touch with our API experts directly, please submit a support ticket.

Each API request has an associated request identifier. You can find this value in the response headers, under Request-Id. You can also find request identifiers in the URLs of individual request logs in your . If you need to contact us about a specific request, providing the request identifier will ensure the fastest possible resolution.

RESTful
Treevox
API key
cURL
POSTMAN
gzipped
JSON
CORS
specific set of modern browsers
Dashboard