📄️ Create a Developer Application
The first step when building an integration is to create a new Developer Application in the Developer Portal. The information you'll need to provide is as follows:
📄️ Authorization
Authorization is the process by which a Clio user grants permission for your application to access their data. In order to use the Clio API, your application must first obtain authorization from the user. Clio implements the OAuth 2.0 specification.
📄️ Permissions
When using Clio's API, there are two layers of permissions to be aware of: access permissions, which relate to what resources your integration has permission to access, and user permissions, which relate to a user's roles within their Clio account.
📄️ Fields
When making a request to the API, you can specify the fields you want to retrieve for each record using the fields parameter. If the parameter isn't included, the response will return a minimal set of default fields for the record(s) being requested. For most endpoints, the id and etag fields are the only default fields returned.
📄️ Rate Limits
Requests to API v4 are rate-limited by access token. This means that after a certain number of requests using the same token in a given time period, the API will return a 429 Too Many Requests response.
📄️ Pagination
Index actions are limited to 200 results per request unless otherwise specified. Where the number of results exceeds 200 records, Clio's API will paginate the results.
📄️ ETags
Etags are identifiers for a specific version of a requested resource. Etags can be used to detect changes between Clio's data and your copy.
📄️ API Changelog
4.0.13
📄️ API Versioning Policy
This document is an overview of how we govern our APIs. Information about all currently supported API versions can be found in the API documentation.