---
title: "Get Access Token"
method: GET
path: "/get_access_token"
tags: ["Get Access"]
---

# Get Access Token

`GET /get_access_token`

## Request

- Base URL: `https://api.developer.atomberg-iot.com/v2`
- URL: `https://api.developer.atomberg-iot.com/v2/get_access_token`
- Auth: API key in header `x-api-key`

Gives you an access token in exchange for your refresh token. The access token is valid for 24 hours, and every other endpoint needs it.

This is the only endpoint that uses the refresh token. It does not use the bearer token from the Authentication panel. Put the refresh token in this request's Authorization field instead. Then put the access token it returns in the panel.

## Request

No query parameters and no request body. Only the two headers below.

| Where | Name | Required | Value |
| --- | --- | --- | --- |
| Header | `x-api-key` | Yes | Your developer API key. |
| Header | `Authorization` | Yes | `Bearer <refresh_token>`. Use the **refresh** token here, not an access token. |

## Response

```json
{
  "status": "Success",
  "message": {
    "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VybmFtZSI6..."
  }
}
```

| Field | Type | Meaning |
| --- | --- | --- |
| `status` | string | `Success` or `Error`. |
| `message.access_token` | string | A JWT valid for **24 hours**. Send it as `Authorization: Bearer <access_token>` on every other endpoint. |

Reuse the token for 24 hours. Each new token uses one call from your quota,
so getting a new token before every request can use up your whole daily
quota.

## Headers

- `Authorization` string, required

## Response `200`

OK

- AccessTokenResponse
  - `status` string: `Success` on a 2xx, `Error` otherwise.
  - `message` object: The response data. Each endpoint has its own format.
    - `access_token` string: A JWT valid for 24 hours. Send it as `Authorization: Bearer <access_token>` on every other endpoint. Reuse it, because each new token uses one call from your quota.

## Other responses

- `401`: The API key or token is missing, malformed or expired, or it is the wrong kind of token.
- `403`: Developer Mode is not enabled for this account, or the user does not exist. You also get a 403 when the URL path or HTTP method is wrong.
- `404`: The device is not on your account, or it has not reported any state yet.
- `429`: You have used up your API key's daily quota, or gone over the per-second limit. The daily quota resets at 00:00 UTC.
- `500`: Something failed on our side. Your request was fine. Try again after a short wait.

## Changes

- **2026-10-06** `30e1ea1bdb73`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/atomberg-iot/apis/atomberg-home-public-apis/changes/get_access_token/get.md)

---

[API](https://skmtc.dev/atomberg-iot/apis/atomberg-home-public-apis.md) - [All operations](https://skmtc.dev/atomberg-iot/apis/atomberg-home-public-apis/llms.txt) - [OpenAPI document](https://skmtc.dev/atomberg-iot/apis/atomberg-home-public-apis/revisions/35290532bede?raw)
