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 first API key (its secret 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 -X POST 'https://socialtap.dev/v1/session' \
-H "x-api-key: $SOCIALTAP_API_KEY" \
-H "content-type: application/json" \
-d '{
"agent_token": "string"
}'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
JSON. Fields marked nullable may be null; optional ones may be left out.
agent_token?stringAn 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
200
Start the dashboard: set up the account
dataobjectShowHide 14 child fields
account_idstringThe account this session acts on: the one x-account-id named, else the person's own.
accountsobject[]Every account the signed-in person belongs to, their own first, then by when they joined: send one's account_id as x-account-id to act on it.
ShowHide 6 child fields
account_idstringThe account (acct_…): send it as x-account-id to act on it.
deletes_atstring date-timenullableWhen the account is deleted for good, RFC 3339 UTC: its owner asked to delete it, and starting the dashboard on it (POST /v1/session with x-account-id) cancels that. null when it isn't being deleted.
joined_atstring date-timeWhen they joined it, RFC 3339 UTC.
objectstringAlways account_membership.
One ofaccount_membership
owner_emailstringIts owner's address, which names it.
rolestringThe person's role in it.
One ofowneradminmember
activated_key_idsstring[]IDs of the agent's pending live keys this call activated (agent_token); [] otherwise.
credits_grantedintegerFree credits this call granted (once per account); 0 otherwise.
deletion_canceled_atstring date-timenullableWhen signing in last canceled this account's scheduled deletion (its API keys stayed revoked: create new ones), RFC 3339 UTC; null when it never was.
emailstringThe signed-in person's verified email address.
expires_atstring date-timeWhen the session ends, RFC 3339 UTC.
free_credits_skippedstringnullableWhy the account this session acts on has no free credits (Account.free_credits_skipped), for its owner; null otherwise.
One ofdisposable_addressdomain_daily_limitnetwork_daily_limitmailbox_used
fresh_untilstring date-timeUntil 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 first key, the first time its dashboard starts); [] otherwise.
ShowHide 17 child fields
created_atstring date-timeWhen the key was created, RFC 3339 UTC.
created_by_keystringnullableThe API key (key_…) that last created this key, gave it the admin scope or rotated it: revoking that key also revokes this one if this one has admin. Null when none did, or a person has rotated it in the dashboard since.
created_by_userstringnullableThe person (GET /v1/members user_id) who created this key in the dashboard, or whose key created it. They may have left the account since. Null when no person did (an operator, or a key from before this was recorded).
dashboardbooleantrue for the account's built-in dashboard key: the dashboard's playground runs as it (so its requests are logged, counted and billed like any key's). Nobody holds its secret, so it works only from the signed-in dashboard. Only its spend_limit can be changed (to cap what the playground spends live); renaming, rescoping, restricting, rotating or revoking it is forbidden (details.reason dashboard_key). It is made on first use and revoked with the account.
expires_atstring date-timenullableWhen the key stops working, RFC 3339 UTC; null when it never expires.
idstringKey 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-timenullableAbout when the key was last used (updated at most hourly); null when never.
namestringYour label for the key.
objectstringAlways api_key.
One ofapi_key
prefixstringThe secret's first characters, to recognize it.
previous_secret_expires_atstring date-timenullableUntil then the secret this key had before its last rotation works too (rotate_secret), RFC 3339 UTC; null when none does.
revoked_atstring date-timenullableWhen the key was revoked; null while it is not.
scopesstring[]What the key may call: endpoints (data endpoints), jobs (create, read and cancel jobs; includes jobs:read), jobs:read (read jobs and their results), account:read (account, usage, ledger, keys), admin (account settings and key management; includes account:read).
One ofendpointsjobsjobs:readaccount:readadmin
secretstringThe key itself: send it in the x-api-key header. Shown only once: store it now.
spend_limitobjectnullableThe key's spend limit and what it used this interval; null when the key has none.
statusstringpending: 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
objectstringAlways session.
One ofsession
rolestringThe signed-in person's role in this account (account_id): what the dashboard lets them do here.
One ofowneradminmember
setup_requiredbooleanWhether POST /v1/session still has this account's setting up to do: a new account's first key (its secret in its answer, once), or the decision on an agent-made account. False in POST /v1/session's own answer once it has done it.
two_factor_enabledbooleanWhether the signed-in person has two-factor authentication on.
metaobjectThe shared route meta (see the API reference introduction).
400
400 Bad Request.
invalid_inputNo retryA parameter is missing or malformed, or the link is not one this endpoint takes.
Fix the parameter named in param as the message says. For a link of the wrong kind, call an endpoint listed in details.endpoints, when there is one.
401
401 Unauthorized.
unauthorizedNo retryThe x-api-key header is missing, or its key is unknown or revoked. On the dashboard's routes: the session cookie is missing or expired.
Send a valid API key in the x-api-key header. No key yet? A person gets one at details.signup_url; an AI agent follows details.agent_auth_url.
403
403 Forbidden.
forbiddenNo retryThe API key is valid but may not make this request, and details.reason says why: the account is suspended, the key lacks the route's scope, waits for its owner to confirm it by email, has expired, or was used from an IP outside its allowlist, or a rotated key's previous secret was used for a call that needs the admin scope. A running job stops with it too 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, so branch on the code.
Act on details.reason. suspended: contact support. scope: use a key with details.required_scope. previous_secret: use the new secret. key_pending: have the owner open the emailed link. key_expired or key_revoked: create a new key. ip_not_allowed: call from an allowed IP.
409
409 Conflict.
idempotency_key_in_progressYes, laterA request with this Idempotency-Key is still running.
Retry after the seconds in the retry-after header to get that request's result.
422
422 Unprocessable.
idempotency_key_reusedNo retryThis Idempotency-Key was already used for a different request (another route or body). Or it was used for this same request, which ran and returned a secret we no longer keep (details.reason answer_expired): running it again would create another.
Use a new Idempotency-Key for a different request, and reuse a key only to retry the identical request. With reason answer_expired, check what the first request created (GET /v1/api_keys, GET /v1/webhook_endpoints) before sending it again under a new key.
429
429 Too Many Requests.
rate_limitedYes, laterThe account passed its runaway-protection ceiling: a high per-account limit that stops a broken client loop (plans have no rate limit). Requests without an API key (signup, the MCP server's tool listing and find_endpoint) are limited per IP address instead. It also stops an account whose failed requests in the last hour cost far more than its successful ones paid for: failures are free within a limit (the message says so), and successes raise it.
Wait the seconds in the retry-after header, then retry. If your steady traffic needs more, ask support to raise the ceiling; without an API key, send one.
operationId session.create