Members
Who is calling
The workspace this credential acts on, and the person behind it for an OAuth token.
GET
/v1/meTL;DR
| Question | Answer |
|---|---|
| What does it do? | Who is calling. |
| What does it need? | An API key or an OAuth access token. |
| What does it take? | Nothing. |
| What does it return? | Status 200 with a body of type Me. |
| In the SDK? | flung.me.get() |
| What can go wrong? | 401 Missing, unknown, revoked or expired API key; 422 The request failed validation; 429 Too many requests for this credential; wait for retry-after seconds. Every failure has the same error shape. |
What it does
The workspace this credential acts on, and the person behind it for an OAuth token. A cheap way for an app to check a token still works.
Example
bash
curl -X GET 'https://api.flung.dev/v1/me' \ --header "Authorization: Bearer $FLUNG_API_KEY"ts
import { Flung } from '@flung.dev/sdk'
const flung = new Flung({ apiKey: process.env.FLUNG_API_KEY! })const result = await flung.me.get()js
const response = await fetch('https://api.flung.dev/v1/me', { method: 'GET', headers: { 'Authorization': `Bearer ${process.env.FLUNG_API_KEY}`, },})if (!response.ok) throw new Error((await response.json()).error.message)const result = await response.json()A successful answer looks like this:
json
{ "workspaceId": "string", "via": "api_key", "userId": "string", "email": "string"}Responses
| Status | Meaning | Body |
|---|---|---|
| 200 | The caller. | Me |
| 401 | Missing, unknown, revoked or expired API key. | Error |
| 422 | The request failed validation. | Error |
| 429 | Too many requests for this credential; wait for retry-after seconds. | Error |
Response body
A 200 answer has the type Me.
| Field | Type | Required | Description |
|---|---|---|---|
workspaceId | string | yes | |
via | "api_key" | "oauth" | yes | How this request authenticated. |
userId | string | null | yes | The person who approved the app, for an OAuth token; null for an API key. |
email | string | null | yes |
See also
| Doc | Why |
|---|---|
| API reference | Every endpoint |
| Schemas | Every request and response type |
| Errors | Every error code and what to do about it |