Vitally's REST API
The public Rest API currently supports creating, updating, retrieving and listing Users, Accounts, Conversations, Tasks, Notes and NPS Responses.
It uses an API Key header for authentication.
List endpoints use cursor-based pagination, ordered by
updatedAt(the default) or
The authentication is passed via the Authorization header on every request.
Keys can be created in the Vitally UI.
For security purposes they can be rolled (a new key will be generated) or deleted.
The Authorization header format is basic auth, using the API Key as the username.
Authorization: Basic c2VjcmV0X2tleTo=
The default rate limiting is set at 1000 requests / min using a sliding window. Headers returned on every request will show the total limit, the requests remaining for the current window, and the number of seconds until the earliest request leaves the window.
RateLimit-Limit: 1000, 1000;window=60
429 Too Many Requests
All paginated endpoints use cursor based pagination.
In addition to an array of results, the response will return a
nextproperty which can be used to access the subsequent page. The
nextproperty will be
nullwhen the end is reached and there are no more pages.
Unless specified otherwise, all List endpoints paginate sorted by
(optional) The number of items to return. The max/default is 100
(optional) The cursor returned from a previous request
(optional) How to order the elements returned. The default is
If you are frequently sending data to Vitally and your data may update at any time, setting
"createdAt"will ensure you return a full list every time.
Any array of the items for that endpoint.
The cursor to use for the following page, if any.
With more results:
At the end:
Fields that are editable in Vitally as rich text (Notes, Tasks) share the same set of supported tags and attributes. Any tags or attributes not in the allow list will be stripped out when creating or updating.