The Movemint API uses OAuth 2.0 for authentication and authorization. All API entity requests require a valid Bearer token.
Supported Grant Types
Grant Type
Use Case
Authorization Code
Server-side applications that can securely store a client secret
Client Credentials
Machine-to-machine communication with no user context
Step 1: Register an OAuth Application
Contact the Movemint team to register your OAuth application. You will receive a Client ID (client_id) and Client Secret (client_secret). You must also provide one or more Redirect URIs where users will be sent after authorizing your application.
Step 2: Authorization Code Flow
Redirect the user's browser to the authorization endpoint:
GET https://www.movemint.cc/oauth/authorize
?client_id=YOUR_CLIENT_ID
&redirect_uri=YOUR_REDIRECT_URI
&response_type=code
&scope=
After the user approves access, they are redirected back to your redirect_uri with an authorization code query parameter:
Access tokens expire after 2 hours (7200 seconds) by default.
Step 4: Refresh an Expired Token
Step 5: Use the Token in API Requests
Include the access token as a Bearer token in the Authorization header:
Revoking Tokens
To revoke an access token or refresh token:
Obtain or refresh an access token
post
Exchange an authorization code or refresh token for an access token. This endpoint supports the authorization_code, refresh_token, and client_credentials grant types.
Body
or
or
Responses
200
Token issued successfully
application/json
access_tokenstringRequired
The access token to use in API requests
token_typestring · enumRequired
Always "Bearer"
Possible values:
expires_inintegerRequired
Token lifetime in seconds (default 7200 = 2 hours)
Example: 7200
refresh_tokenstringOptional
Token used to obtain a new access token when the current one expires. Not present for client_credentials grants.
created_atintegerRequired
Unix timestamp of when the token was created
400
Invalid grant or request
application/json
401
Invalid client credentials
application/json
post
/oauth/token
Revoke a token
post
Revoke an access token or refresh token. After revocation, the token can no longer be used to access protected resources.
Body
tokenstringRequired
The access token or refresh token to revoke
client_idstringRequired
Your application's Client ID
client_secretstringRequired
Your application's Client Secret
Responses
200
Token revoked successfully (always returns 200, even if the token was already revoked)
No content
400
Invalid request
application/json
post
/oauth/revoke
No content
Get token info
get
Retrieve metadata about the current access token, including its scopes, expiration, and associated resource owner and application.
Authorizations
AuthorizationstringRequired
Pass the access token in the Authorization header: