This document describes the resources that make up the TeamSnap API.
All API access is over HTTPS, and available via
It is highly recommended that you enforce certificate validation to ensure the security of your services and your users.
TeamSnap's API is a Collection+JSON API. This differs from your normal RESTful style JSON API in a few very important ways:
More information on how Collection+JSON works and how it applies to this API is available on the Collection+JSON page of this documentation.
The most common response codes will be in the
200 OKCall completed successfully.
201 CREATEDObject created successfully.
204 NO RESPONSECall completed, no response required.
401 UNAUTHORIZEDYou are not authorized to access this resource. Try re-authorizing.
404 NOT FOUNDThis resource does not exist, or you may be unauthorized. Try re-authorizing; if that fails, clear your URI cache.
411 Length RequiredYou need to add a Content Length header to your request.
429 TOO MANY REQUESTSYou have reached your rate limit.
500Server took a brief vacation.
All dates and times (including timestamps) are in ISO 8601 Format.
Blank fields are sent as
null instead of being omitted from responses.
The TeamSnap API versioning scheme adheres to the guidelines set out in SemVer 2.0.0. The version of the API is available in each request under the
version field. Version is global across the API, resources are not versioned individually.
To construct a request, you will need to obtain an authorization token.