API Reference
The endpoints documented here are internal. They exist to power VAAST license validation and payload library sync, and they are reached only by the VAAST desktop app and the Xtrinel dashboard. They are not public APIs — there is no API key flow, no SDK, and no stability guarantee for external callers.
This page exists so that customers evaluating VAAST in locked-down network environments can audit exactly what the app talks to. The base URL in all cases is:
https://api.xtrinel.com
Auth is Microsoft Entra ID: every request carries an access token
in Authorization: Bearer … bound to the signed-in user.
GET /v1/license/validate
Returns the plan and entitlements for the current user. VAAST calls this on sign-in and on every app launch. The response is the authoritative source for whether the client is allowed to sync the Pro payload library or run authenticated scans.
Example response:
{
"plan": "pro",
"valid": true,
"renews_at": "2026-05-14T00:00:00Z",
"entitlements": {
"live_payload_sync": true,
"authenticated_scanning": true
}
}
A plan of "free" is still a valid state — it just means the
client gets the baseline library and nothing else.
GET /v1/payloads/manifest
Returns the current payload library manifest: a list of payload file ids, versions, SHA-256 hashes, and download URLs. VAAST compares the manifest against the locally cached library and pulls down any file whose hash changed.
The manifest is scoped to the caller's plan: Free accounts always receive the baseline-only manifest, regardless of entitlements on other endpoints. This is so that a revoked Pro license cleanly falls back to the baseline library on the next sync.
Example response:
{
"library_version": "2026.04.14",
"payloads": [
{
"id": "pi.direct.role-override.v1",
"category": "prompt_injection",
"severity": "high",
"sha256": "…",
"url": "https://api.xtrinel.com/v1/payloads/pi.direct.role-override.v1.yaml"
}
]
}
PATCH /v1/users/me
Updates the signed-in user's profile. Called from the VAAST Settings screen and from the Xtrinel dashboard when the user changes their display name or toggles marketing email opt-in. Request body fields are all optional:
{
"display_name": "Sam Practitioner",
"marketing_opt_in": false
}
A successful response returns the full updated user record.
Not documented here
Billing, checkout, portal, and webhook endpoints live on the same API but are only called by the Xtrinel dashboard. They are not reached by the VAAST desktop app and are therefore out of scope for this reference.