Getting Started

API Status:
API Status:
API Status:
Weekly API Changelog
Want to be notified about changes in the TeamSnap API?
Sign up here to receive our weekly changelog newsletter


This document describes the resources that make up the TeamSnap API.

Getting Started


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:

  1. The client should not construct any URIs.
  2. Caching of URIs is permitted; however, if an error is encountered, this cache should be cleared.
  3. Every JSON object returned will be a collection.

More information on how Collection+JSON works and how it applies to this API is available on the Collection+JSON page of this documentation.

Response Codes

The most common response codes will be in the 200 and 400 ranges.

Successful Calls:

Unsuccessful Calls:

Date and Time

All dates and times (including timestamps) are in ISO 8601 Format.

Null Data

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.

Constructing a Request

To construct a request, you will need to obtain an authorization token.