logologo
Pricing
AppsPartnersAbout
Log inStart free trial

Authentication & scopes

How to authenticate REST and MCP requests to WEXTL, the scope model, and least-privilege guidance for Personal Access Tokens.

Region*Select

Updates every sample URL on this page to your organization’s regional host. Match the shard in your API key (wextl_<shard>_…).

Personal Access Tokens (PAT)

Mint a token from Dashboard → API and send it as a bearer credential on every request. A token acts on behalf of the member who created it — actions taken with it are attributed to "{creator} via API key {name}" in your organization's activity log.

text
Authorization: Bearer wextl_...

OAuth 2.1

Hosted AI clients (claude.ai, ChatGPT) connect via OAuth 2.1 with dynamic client registration instead of a pasted token. You approve an organization + scope grant once during the consent flow; the client then holds a short-lived access token it refreshes automatically.

Scope model

Every scope is a pair of an entity type (workflow, credential, database, variable, structure, function) and an action (read or write). Grant the narrowest set of scopes a token needs — a read-only integration should never hold a write scope it doesn't use. Team and folder discovery tools use `workflow:read`; webhook minting uses `workflow:write`.

  • Least privilege: pick read-only scopes whenever your integration only inspects data.
  • Per-stage checks: some actions (e.g. using a credential for live options) require credential:use-level write, not just credential:read.
  • When create_credential returns a connect_url, a logged-in org member completes the form; the agent then polls list_credentials.

Rotating a key

Rotate a Personal Access Token without downtime: mint a new token, update your integration to use it, confirm calls succeed with the new token, then revoke the old one. The per-organization key cap allows both tokens to exist briefly during the cut-over.

Working across multiple organizations

A key or OAuth grant is scoped to exactly one organization and its regional endpoint. To integrate with N organizations, mint N tokens (or complete N OAuth grants) — one connection per organization.

Offboarding a member

When a member who granted an OAuth connection leaves the organization or is demoted below admin, their grants stop working the next time they're used — access is re-checked against their current role on every request, so there's nothing extra to revoke by hand.