Authentication via API (Classic)
To interact with MightyCall API, you must first authenticate your request by obtaining an authorization token. Authentication is performed by sending a POST request to:
https://api.mightycall.com/v4/auth/token
This endpoint returns a bearer token, which is required to access all other API methods. The token is valid for 24 hours, after which it must be refreshed or reissued.
There are 2 ways Classic customers can authenticate via API:
-
By using their API key + User key, if they have a User key generated and toggled on in API integration;
-
By using their API key + extension, if they don’t have a User key generated and toggled on in API integration.
So, for John here we will use the first method, and for Peter – the second one.
-
Create a new HTTPS request in your API client (we're using Postman here).

- Select a method for your API request (we'll need POST for this case) and enter the endpoint: https://api.mightycall.com/v4/auth/token

- In the Headers tab, add the following information:
Key
Value
x-api-keyThe API key that from your account's API Integration section
Content-Typeapplication/x-www-form-urlencoded
- In the Body tab select x-www-form-urlencoded and enter the following:
John is using his User key asKey
Value
grant_typeclient_credentialsclient_idThe API key that from your account's API section
client_secretYour User key or extension
client_secret:
Peter is using his extension asclient_secret:
- Click to Send the request. As a result, you should receive a 200 OK response containing your access_token (bearer token) valid for 24 hours, of which can be used for authorization in further API requests.

- You can use refresh_token to include in the body of your new authentication API request: it will regenerate the bearer token and reset the 24 life cycle timer. In that case, you will need to change
grant_typetorefresh_tokenand remove other parameters from the Body tab: