Validate Token
AI-generatedSummary
Checks whether an API token is valid for a given zone and minimum permission level by POSTing to the Auth Service's /validate endpoint, and returns the service's response as-is.
Inputs
- Token (required) — The API token to validate (masked password field). Sent in the request body.
- Zone (required) — The zone (area) to validate against. Options are loaded dynamically from the Auth Service's /tokens/zones endpoint using the configured credentials. Sent as
area. - Permission Level (required) — Minimum permission level required: Read, Write, Delete, or All. Defaults to Read.
Output shape
One output item per input item, with the JSON body returned by the Auth Service /validate endpoint as the item's json.
The exact response fields are defined by the Auth Service and not specified in the node. The validate request is sent via plain httpRequest without the credential's authentication; the credential is used only for the base URL (trailing slashes are stripped). A non-2xx response throws an error, unless Continue On Fail is enabled, in which case the item is
{error, operation}. The Zone dropdown needs valid credentials to populate; otherwise it shows a placeholder with an empty value.
Examples
Example 1: Gate a webhook workflow by checking the caller's bearer token before processing.
Token: {{$json.headers.authorization}} (expression), Zone: orders, Permission Level: write. Follow with an IF node on the validation result.
Example 2: Verify a token has full access to the billing zone.
Token: pasted or expression value, Zone: billing, Permission Level: All.