Connection identity
Validate the current API key and retrieve the account associated with it. Use this endpoint to test a connection and identify the account in your integration.
GET
/v1/meBearer tokenNo query parameters or request body are required.
Request
sh
curl 'https://api.meetzi.co/v1/me' \
--header "Authorization: Bearer $MEETZI_API_KEY"Response
200 OK · A JSON object, without a data wrapper.
json
{
"userId": "11111111-1111-4111-8111-111111111111",
"email": "alex@example.com",
"name": "Alex Morgan",
"displayLabel": "alex@example.com",
"apiKeyId": "22222222-2222-4222-8222-222222222222",
"provider": "zapier"
}| Field | Type | Description |
|---|---|---|
userId | string | ID of the user who owns the API key. |
email | string or null | Account email, when available. |
name | string or null | Profile name, when available. |
displayLabel | string | Account email; falls back to name, then user ID. |
apiKeyId | string | ID of the key record, not the secret key. |
provider | string | Provider associated with the key. Keys currently generated through the Zapier integration return zapier, including when used by a custom client. |
Errors
| Status | Meaning |
|---|---|
401 | Missing, invalid, or revoked API key. |
500 | Authentication failure, or Failed to load Zapier connection info. |
See the shared error formats.