Get the current identity

curl --request GET \
  --url https://api.awardee.dev/v1/me \
  --header 'Authorization: Bearer <token>'

{
  "object": "<string>",
  "connection_label": "<string>",
  "org_name": "<string>",
  "auth": {
    "type": "<string>"
  },
  "org": {
    "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "name": "<string>",
    "slug": "<string>"
  },
  "api_key": {
    "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "name": "<string>"
  }
}

Endpoints

Get the current identity

Returns the identity behind the credential used on this request. Any valid API key or OAuth token works — no extra scope is required. The response shape varies by credential: an API key yields auth.type: "api_key" with the authenticating api_key, while an OAuth token yields auth.type: "oauth_token" with the granting client, the consenting user, and the token’s scopes. Both variants include the resolved org plus flat connection_label / org_name helpers for clients (such as Zapier) that label connections.

GET

curl --request GET \
  --url https://api.awardee.dev/v1/me \
  --header 'Authorization: Bearer <token>'

{
  "object": "<string>",
  "connection_label": "<string>",
  "org_name": "<string>",
  "auth": {
    "type": "<string>"
  },
  "org": {
    "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "name": "<string>",
    "slug": "<string>"
  },
  "api_key": {
    "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "name": "<string>"
  }
}

Authorizations

Authorization

string

header

required

Send your API key as Authorization: Bearer aw_live_…. Manage keys in the dashboard under Settings → API Keys.

Response

Current identity

Option 1
Option 2

object

string

required

Allowed value: "me"

connection_label

string

required

org_name

string

required

auth

object

required

Show child attributes

org

object

required

Show child attributes

api_key

object

required

Show child attributes

Verify your key Authentication