Tilia APIs are the primary means for developers to access the Tilia resources and perform tasks such as registering users, creating invoices, and requesting payouts.
All of our APIs are based on REST architecture and are accessed via HTTPS at specified URLs. Our APIs use JSON as their communication format and the standard HTTP methods like GET, PUT, POST, and DELETE. Refer to the API Reference for the methods available for each endpoint.
URIs for Tilia's APIs have the following structure:
In these URIs:
api_nameis the name of the API, for example,
environmentis the Tilia environment you are working with. Staging is
staging.tilia-inc.com, while Production is
versionis the version of the API or endpoint. Versions are represented as the letter
vfollowed by the version number, for example,
v2. Each API endpoint shows the correct version in its usage documentation.
resource_idis the unique identifier for the resource.
resourceis the relative path defined for the resource.
Here are some examples to illustrate the URI structure:
All Tilia API requests must be made over HTTPS. Calls made over HTTP will fail.
The Staging environment mirrors the Tilia Production environment, supporting all of the same API endpoints. Applications should be tested against the Staging environment before being used in production. Here are some key differences from the Production environment:
- The Staging environment contains test data and is completely separate from your Production environment.
- Actual money is not sent or received as part of test transactions. Real financial data should not be used in Staging.
- Test payment methods may only be used in Staging.
Non-breaking changes may be introduced to an existing version. Updates are versioned if those updates are considered breaking changes. You can retrieve current version information for each API by appending /info to the API's base URI, for example,