Skip to content
  • There are no suggestions because the search field is empty.

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.

  1. Create a new HTTPS request in your API client (we're using Postman here).

     

    2026-03-25_15-13

  2. 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

    2025-10-28_13-42
  3. In the Headers tab, add the following information:

    Key

    Value

    x-api-key

    The API key that from your account's API Integration section

    Content-Type

    application/x-www-form-urlencoded

    2025-10-28_13-51
  4. In the Body tab select x-www-form-urlencoded and enter the following:

    Key

    Value

    grant_type

    client_credentials

    client_id

    The API key that from your account's API section

    client_secret

    Your User key or extension

    John is using his User key as client_secret:

    2025-10-28_13-57
    Peter is using his extension as client_secret:

    2025-10-28_14-19
  5. 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.

    2025-10-28_14-12
  6. 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_type to refresh_token and remove other parameters from the Body tab:

    2025-10-28_18-29