📄️ OAuth Applications
The first step when building an integration with the Clio Platform API (Grow API) 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 Platform API, your application must first obtain authorization from the user. The Clio Platform API implements the OAuth 2.0 specification using the Authorization Code grant type.
📄️ Permissions
Though we refer to them as "permissions" in this document, this concept is interchangeable with that of OAuth scopes. If you're unfamiliar with scopes, see oauth.com's article as a starting point.
📄️ Rate Limits
The Clio Platform API enforces rate limits to ensure fair usage and maintain service reliability for all integrators. This document explains how rate limiting works, what to expect when limits are exceeded, and best practices for building resilient integrations.
📄️ Pagination
Index actions are limited to 200 results per request unless otherwise specified. Where the number of results exceeds 200 records, the Clio Platform 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
📄️ API Versioning Policy
This document is an overview of how we govern the Clio Platform API versioning.