Skip to content
BuildBase
HTTP API menu

Start or resume the monday.com app authorization hand-off

No router-level gate: the token query value must be a JWT signed with the org's monday.com signing secret.

Warning

Not fully described yet. The API description has no described successful answer for this operation yet. The method, path, sign-in, rate limits and request fields on this page are read from the server's code and are accurate; what a successful call returns is not written down here yet. Until it is, search engines and the agent index leave this page out.

GET/api/v1/auth/monday.com/authorize/orgId

Sign-in
None at the router: the operation is public, or checks its own proof (a signature, a token in the body, a signed link).
Rate limit
Up to 500 requests every 3 seconds per IP address; up to 1,000 requests a minute per API key (some requests are not counted).

No router-level gate: the token query value must be a JWT signed with the org's monday.com signing secret. If a valid stored token exists for that monday user, redirects to the app's authentication URL (or monday's backToUrl) with a signed hand-off; otherwise sets a per-state browser cookie and redirects to monday.com's consent screen.

Request

Path parameters

FieldTypeRequiredConstraintsDescription
orgIdstringYes--

Example request

Replace each YOUR_... value with your own.

curl -X GET "https://api.console.buildbase.app/api/v1/auth/monday.com/authorize/YOUR_ORG_ID"
const response = await fetch(
  'https://api.console.buildbase.app/api/v1/auth/monday.com/authorize/YOUR_ORG_ID',
  {
    method: 'GET',
  }
);
if (!response.ok) {
  throw new Error(`${response.status}: ${await response.text()}`);
}
const data = await response.text();
import requests

response = requests.get(
    "https://api.console.buildbase.app/api/v1/auth/monday.com/authorize/YOUR_ORG_ID",
    timeout=30,
)
response.raise_for_status()
data = response.text

Responses

A successful answer is not described yet. The server answers with the status and body its handler sends.

Any other status

The handler's own answer. Not described yet: response bodies come from captured responses (server/openapi/captured) and overlays (server/openapi/overlays).

Errors

Each refusal, what it means, and what to do. The request changed nothing.

400 Bad Request

What it means: The request failed a validate() schema, or an id in the path is not a valid id. path names the field.

What to do: Fix the field the body names in path (or read message) and send the request again. Nothing was changed.

Example
{
  "error": true,
  "success": false,
  "path": "string",
  "message": "string"
}

404 Not Found

What it means: An id in the path names nothing in this org.

What to do: Check the ids in the path: one of them names nothing in this organization.

Example
{
  "success": false,
  "message": "string"
}

429 Too Many Requests

What it means: A rate limit in x-rateLimit was reached. retryAfter and the Retry-After header say how many seconds until the window resets.

What to do: Wait the number of seconds in the Retry-After header (also retryAfter in the body), then retry. Slow down repeated calls.

Example
{
  "success": false,
  "message": "string",
  "reason": "rate_limited",
  "retryAfter": 1
}