Our API is accessible at over HTTPS.


During the evolution of this API, there will be different API versions. The current API version is v1 and can be accessed at

Response Formats

At the moment we only support JSON response format. (XML will be available in the future)

Error Codes

Code Text Description
200 OK Success
201 Created Resource was created
304 Not Modified There was no new data to return.
400 Bad Request The request was invalid. An accompanying error message will explain why.
401 Unauthorized Authentication credentials were missing or incorrect.
402 Payment required The request is not available in your current price plan.
403 Forbidden The request is understood, but it has been refused.
404 Not Found The URI requested is invalid or the resource requested, such as a pass, does not exists.
422 Unprocessable Entity The request was well-formed but was unable to be followed due validation errors.
500 Internal Server Error Something is broken. Please contact support so that our developer team can investigate.


In order to secure your passes, all communication with the API must be encrypted using HTTPS transport protocol.

Make sure that you verify our SSL certificate on your client side. Otherwise someone might be able to steel your API key and create passes on your behalf.


You need to authenticate your API request using an App Key. You can create multiple app keys with different access permission to your pass templates and/or pass type ids.

The app key can be send as the user (basic authorization) or directly in the authorization header of your request.
Here is an example on how to do this with cURL: curl -u <APP-KEY>: (Please note the :)

Ready to start?

REST Resources