Start the dashboard: set up the account · SocialTap API reference

The dashboard calls it once it is signed in (people sign in with Google, GitHub or an email address and password on the sign-in page). The first call of a new account returns its live and test keys (secrets shown only here); with agent_token, it approves that agent signup, activating the agent's pending live key and granting the free credits. An account an agent opened that its owner signs in to without approving the agent gets fresh keys, and the agent's are revoked. Free.

Auth: the dashboard session cookie.

Send an idempotency-key header to retry safely: the same key and body within 1 day never repeat the work.

Example

cURL

curl -X POST 'https://staging.socialtap.dev/v1/session' \
  -H "x-api-key: $SOCIALTAP_API_KEY" \
  -H "content-type: application/json" \
  -d '{
  "agent_token": "string"
}'

Authorizations

The dashboard's session cookie, not an API key.

Headers

Name	Type	Description	Example
`idempotency-key` optional	`string` max 255 chars	On any POST: your unique key for the request (1–255 printable ASCII characters; a UUID is ideal), kept 24 hours. Retrying with the same key and body never repeats the work: the answer is the first request's result, in its current state.	—

idempotency-keystringmax 255 chars

On any POST: your unique key for the request (1–255 printable ASCII characters; a UUID is ideal), kept 24 hours. Retrying with the same key and body never repeats the work: the answer is the first request's result, in its current state.

Body

application/json

JSON. Fields marked nullable may be null; optional ones may be left out.

Field	Type	Description
`agent_token?`	`string`	An agent signup's confirmation token (after # on the agent confirmation page): approves that agent, activating its pending live key. Only the signed-in owner of the address the agent named can use it.

agent_token?string

An agent signup's confirmation token (after # on the agent confirmation page): approves that agent, activating its pending live key. Only the signed-in owner of the address the agent named can use it.

Response

application/json

200

Start the dashboard: set up the account

Field	Type	Description
`data`	`object`
`data.account_id`	`string`	The signed-in account.
`data.activated_key_ids`	`string[]`	IDs of the agent's pending live keys this call activated (agent_token); [] otherwise.
`data.credits_granted`	`integer`	Free credits this call granted (once per account); 0 otherwise.
`data.email`	`string`	The signed-in person's verified email address.
`data.expires_at`	`string` (date-time)	When the session ends, RFC 3339 UTC.
`data.fresh_until`	`string` (date-time)	Until when this session may create API keys and change keys without re-verifying (password or two-factor code), RFC 3339 UTC.
`data.new_api_keys`	`object[]`	Keys this call created, with their secrets shown only here (a new account's live and test keys, the first time its dashboard starts); [] otherwise.
`data.new_api_keys[].created_at`	`string` (date-time)	When the key was created, RFC 3339 UTC.
`data.new_api_keys[].expires_at`	`string` (date-time) or `null`	When the key stops working, RFC 3339 UTC; null when it never expires.
`data.new_api_keys[].id`	`string`	Key ID (key_…): manage the key with it. It is not the secret.
`data.new_api_keys[].ip_allowlist`	`string[]`	IP addresses or CIDR ranges (IPv4 or IPv6) the key works from; [] = any.
`data.new_api_keys[].last_used_at`	`string` (date-time) or `null`	About when the key was last used (updated at most hourly); null when never.
`data.new_api_keys[].mode`	`string`	live keys spend credits on real requests; test keys answer from recorded responses, free. One of `live`, `test`
`data.new_api_keys[].name`	`string`	Your label for the key.
`data.new_api_keys[].object`	`string`	Always api_key. One of `api_key`
`data.new_api_keys[].prefix`	`string`	The secret's first characters, to recognize it.
`data.new_api_keys[].revoked_at`	`string` (date-time) or `null`	When the key was revoked; null while it is not.
`data.new_api_keys[].scopes`	`string[]`	What the key may call: endpoints (data endpoints), jobs, account:read (account, usage, ledger, keys), admin (account settings and key management; includes account:read). One of `endpoints`, `jobs`, `account:read`, `admin`
`data.new_api_keys[].secret`	`string`	The key itself: send it in the x-api-key header. Shown only once: store it now.
`data.new_api_keys[].spend_limit`	`object` or `null`	The key's spend limit and what it used this interval; null when the key has none.
`data.new_api_keys[].status`	`string`	pending: created by an agent signup and waiting for the owner's email confirmation (it can only read GET /v1/account). expired: past expires_at. One of `active`, `pending`, `expired`, `revoked`
`data.object`	`string`	Always session. One of `session`
`data.two_factor_enabled`	`boolean`	Whether the signed-in person has two-factor authentication on.
`meta`	`object`	The shared route meta (see the API reference introduction).

dataobject

Show 9 child fields

account_idstring

The signed-in account.

activated_key_idsstring[]

IDs of the agent's pending live keys this call activated (agent_token); [] otherwise.

credits_grantedinteger

Free credits this call granted (once per account); 0 otherwise.

emailstring

The signed-in person's verified email address.

expires_atstring date-time

When the session ends, RFC 3339 UTC.

fresh_untilstring date-time

Until when this session may create API keys and change keys without re-verifying (password or two-factor code), RFC 3339 UTC.

new_api_keysobject[]

Keys this call created, with their secrets shown only here (a new account's live and test keys, the first time its dashboard starts); [] otherwise.

Show 14 child fields

created_atstring date-time

When the key was created, RFC 3339 UTC.

expires_atstring date-timenullable

When the key stops working, RFC 3339 UTC; null when it never expires.

idstring

Key ID (key_…): manage the key with it. It is not the secret.

ip_allowliststring[]

IP addresses or CIDR ranges (IPv4 or IPv6) the key works from; [] = any.

last_used_atstring date-timenullable

About when the key was last used (updated at most hourly); null when never.

modestring

live keys spend credits on real requests; test keys answer from recorded responses, free.

One oflivetest

namestring

Your label for the key.

objectstring

Always api_key.

One ofapi_key

prefixstring

The secret's first characters, to recognize it.

revoked_atstring date-timenullable

When the key was revoked; null while it is not.

scopesstring[]

What the key may call: endpoints (data endpoints), jobs, account:read (account, usage, ledger, keys), admin (account settings and key management; includes account:read).

One ofendpointsjobsaccount:readadmin

secretstring

The key itself: send it in the x-api-key header. Shown only once: store it now.

spend_limitobjectnullable

The key's spend limit and what it used this interval; null when the key has none.

statusstring

pending: created by an agent signup and waiting for the owner's email confirmation (it can only read GET /v1/account). expired: past expires_at.

One ofactivependingexpiredrevoked

objectstring

Always session.

One ofsession

two_factor_enabledboolean

Whether the signed-in person has two-factor authentication on.

metaobject

The shared route meta (see the API reference introduction).

400

400 Bad Request.

Code	HTTP	Retry	Meaning	What to do
`invalid_input`	400	No	The request parameters are missing or malformed, or the URL is not a supported link for this endpoint.	Fix the parameter named in param (the message says how); for a link of the wrong kind, call the endpoint the message names.

invalid_inputNo retry

The request parameters are missing or malformed, or the URL is not a supported link for this endpoint.

Fix the parameter named in param (the message says how); for a link of the wrong kind, call the endpoint the message names.

401

401 Unauthorized.

Code	HTTP	Retry	Meaning	What to do
`unauthorized`	401	No	The x-api-key header is missing, unknown or revoked (or, on the dashboard's routes, the session cookie is missing or expired).	Send a valid API key in the x-api-key header; without one, get a key at details.signup_url (AI agents: POST details.agent_signup_url).

unauthorizedNo retry

The x-api-key header is missing, unknown or revoked (or, on the dashboard's routes, the session cookie is missing or expired).

Send a valid API key in the x-api-key header; without one, get a key at details.signup_url (AI agents: POST details.agent_signup_url).

403

403 Forbidden.

Code	HTTP	Retry	Meaning	What to do
`forbidden`	403	No	The API key is valid but may not make this request: its account is suspended, its scopes do not include the route, it is waiting for its owner's email confirmation, it is past its expiry, or the request came from an IP its allowlist does not include. A running job stops the same way when its account is suspended or the key that created it is revoked or expires. It is about the key, never the item (a private item is private_or_unavailable, also 403): branch on the code.	Do what details.reason says: if suspended, contact support; otherwise use a key whose scopes cover the route (details.required_scope), have the owner confirm the emailed link, create a new key, or call from an allowed IP.

forbiddenNo retry

The API key is valid but may not make this request: its account is suspended, its scopes do not include the route, it is waiting for its owner's email confirmation, it is past its expiry, or the request came from an IP its allowlist does not include. A running job stops the same way when its account is suspended or the key that created it is revoked or expires. It is about the key, never the item (a private item is private_or_unavailable, also 403): branch on the code.

Do what details.reason says: if suspended, contact support; otherwise use a key whose scopes cover the route (details.required_scope), have the owner confirm the emailed link, create a new key, or call from an allowed IP.

409

409 Conflict.

Code	HTTP	Retry	Meaning	What to do
`idempotency_key_in_progress`	409	Yes, later	A request with this Idempotency-Key is still running.	Retry after the number of seconds in the retry-after header to get that request's result.

idempotency_key_in_progressYes, later

A request with this Idempotency-Key is still running.

Retry after the number of seconds in the retry-after header to get that request's result.

422

422 Unprocessable.

Code	HTTP	Retry	Meaning	What to do
`idempotency_key_reused`	422	No	The Idempotency-Key was already used with a different request (another route, or another body).	Send a new Idempotency-Key for a different request; reuse a key only to retry the identical request.

idempotency_key_reusedNo retry

The Idempotency-Key was already used with a different request (another route, or another body).

Send a new Idempotency-Key for a different request; reuse a key only to retry the identical request.

429

429 Too Many Requests.

Code	HTTP	Retry	Meaning	What to do
`rate_limited`	429	Yes, later	The account exceeded its runaway-protection ceiling: plans do not limit request rate, but a high per-account safety ceiling stops broken client loops. Support raises it on request. Without an API key (signup, the MCP server's tool listing and find_endpoint), requests are limited per IP address instead.	Wait for the number of seconds in the retry-after header, then retry; ask support to raise the ceiling if your sustained traffic needs more (calls without an API key: use one).

rate_limitedYes, later

The account exceeded its runaway-protection ceiling: plans do not limit request rate, but a high per-account safety ceiling stops broken client loops. Support raises it on request. Without an API key (signup, the MCP server's tool listing and find_endpoint), requests are limited per IP address instead.

Wait for the number of seconds in the retry-after header, then retry; ask support to raise the ceiling if your sustained traffic needs more (calls without an API key: use one).

operationId session.create