Authentication
Supported Grant Types
Step 1: Register an OAuth Application
Step 2: Authorization Code Flow
GET https://www.movemint.cc/oauth/authorize
?client_id=YOUR_CLIENT_ID
&redirect_uri=YOUR_REDIRECT_URI
&response_type=code
&scope=https://your-app.com/callback?code=AUTHORIZATION_CODEStep 3: Exchange the Code for Tokens
curl -X POST https://www.movemint.cc/oauth/token \
-d grant_type=authorization_code \
-d code=AUTHORIZATION_CODE \
-d client_id=YOUR_CLIENT_ID \
-d client_secret=YOUR_CLIENT_SECRET \
-d redirect_uri=YOUR_REDIRECT_URIStep 4: Refresh an Expired Token
Step 5: Use the Token in API Requests
Revoking Tokens
Token issued successfully
The access token to use in API requests
Always "Bearer"
Token lifetime in seconds (default 7200 = 2 hours)
7200Token used to obtain a new access token when the current one expires. Not present for client_credentials grants.
Unix timestamp of when the token was created
Invalid grant or request
Invalid client credentials
The access token or refresh token to revoke
Your application's Client ID
Your application's Client Secret
Token revoked successfully (always returns 200, even if the token was already revoked)
No content
Invalid request
No content
Pass the access token in the Authorization header:
Authorization: Bearer YOUR_ACCESS_TOKEN
Token information
The ID of the athlete who authorized the token
List of scopes granted to this token
Seconds until the token expires
Unix timestamp of when the token was created
Token is invalid or expired
Last updated