---
title: "Me"
description: "Find out which Pallyy account the API key or connected-app token you are calling with belongs to."
category: "endpoints"
emoji: "🙋"
order: 6
datePublished: "2026-09-28"
dateUpdated: "2026-09-28"
---

Every API key and every connected-app access token belongs to one Pallyy account. This endpoint tells you which one, without needing anything else: no `socialSetId`, no scopes.

Use it to check that a credential works, or to know your own account id. That id is what `ownedBy` on a [social set](/docs/api/social-sets) is compared against: a set whose `ownedBy` is not your id was shared with you through a team invite, and posts or uploads into it count against the owner's plan.

## Get the current account

```
GET /v1/me
```

```bash
curl https://app.pallyy.com/api/v1/me \
  -H "Authorization: Bearer pallyy_your_api_key"
```

```json
{
  "userId": "665f1c2ab7e2a4d1f0a1b2c0"
}
```

| Field | Type | Meaning |
| --- | --- | --- |
| `userId` | string | The id of the account that owns the key, or that authorized the connected app |

The request counts toward your [rate limit](/docs/api/rate-limits) like any other call. An invalid, disabled, or revoked credential receives the usual `401`, see [errors](/docs/api/errors).