Identity (me)

Return the user and organization identity associated with the current access token.

GET/oauth-me

These endpoints are used by third-party OAuth integrations (such as Zapier). If you are building a direct server integration, use an API key instead.

Try it

GET

API Key (stored locally in your browser only)

Create an API key in your workspace under Settings → Integrations & API.

Query

None.

Zapier and similar platforms call this immediately after the OAuth dance to display the connected account in the UI ("Connected as Acme").

Works with both Bearer tokens and API keys.

Example request

bash

curl -X GET 'https://api.wundertreos.com/functions/v1/oauth-me' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Response

json

{
  "id": "u1b1f3a0-4d2e-4f9a-9b1c-2d4e5f6a7b8c",
  "email": "jane@acme.com",
  "org_id": "a1b2c3d4-1111-2222-3333-444455556666",
  "org_name": "Acme Inc",
  "org_slug": "acme"
}

Response

Field	Type	Description
`id`	uuid	The authenticated user's ID. For API keys, this is the user who created the key (may be empty if the key was created without a user context).
`email`nullable	string	The user's email.
`org_id`	uuid	The organization this credential is scoped to.
`org_name`	string	Display name of the organization.
`org_slug`nullable	string	URL‑friendly slug.

PreviousRevoke Next Scopes