Ir al contenido
dotby Docs

Me

Esta página aún no está disponible en tu idioma.

Call GET /v1/me first. It tells you who the token belongs to and which workspaces you can act in — ids, slugs, your role, and each workspace’s plan.

Who am I

Section titled “Who am I”

Return the signed-in dotby user and the workspaces they belong to (with ids, role, and plan). Call this first to discover workspace ids and which workspaces are Pro-eligible for the connector.

GET /v1/me

Terminal window
curl -H "Authorization: Bearer $DOTBY_TOKEN" \
  "https://api.dotby.app/v1/me"

Response: the resulting object as JSON.

Errors

Section titled “Errors”

Every error is an RFC 9457 application/problem+json body with a machine-stable code. Branch on the code, not the message:

  • 401 — unauthenticated / invalid_token: the bearer token is missing, expired, or revoked. Re-authenticate; do not retry as-is.
  • 403 — insufficient_scope / forbidden / upgrade_required: the token works but may not do this. upgrade_required means the workspace is not on Pro.
  • 404 — not_found_or_forbidden: the resource does not exist for this token. Never probe for existence.
  • 409 — idempotency_conflict: same Idempotency-Key, different body. Mint a new key.
  • 429 — rate_limited: back off for the number of seconds in Retry-After, then retry.
  • 400 — validation_failed: the request shape is wrong. Fix the request; retrying unchanged will fail again.