drchrono.com

api:drchrono.com · vv4 (Hunt Valley) · source: apis.guru

This document is intended as a detailed reference for the precise behavior of the drchrono API. If this is your first time using the API, start with our tutorial . If you are upgrading from a previous version, take a look at the changelog section. Authorization Initial authorization There are three main steps in the OAuth 2.0 authentication workflow: 1. Redirect the provider to the authorization page. 2. The provider authorizes your application and is redirected back to your web application. 3. Your application exchanges the authorization code that came with the redirect for an access token and refresh token . Step 1: Redirect to drchrono The first step is redirecting your user to drchrono, typically with a button labeled "Connect to drchrono" or "Login with drchrono". This is just a link that takes your user to the following URL: https://drchrono.com/o/authorize/?redirect uri=REDIRECT URI ENCODED&response type=code&client id=CLIENT ID ENCODED&scope=SCOPES ENCODED - REDIRECT URI ENCODED is the URL-encoded version of the redirect URI (as registered for your application and used in later steps). - CLIENT ID ENCODED is the URL-encoded version of your application's client ID. - SCOPES ENCODED is a URL-encoded version of a space-separated list of scopes, which can be found in each endpoint or omitted to default to all scopes. The scope parameter consists of an optional, space-separated list of scopes your application is requesting. If omitted, all scopes will be requested. Scopes

[![Connect-MCP](https://clawy.uk/mcp/badge/api%3Adrchrono.com.svg)](https://clawy.uk/mcp/s/api%3Adrchrono.com)