QyzarQyzar/

Docs

Dashboard

Start

  • Overview
  • Quick start

SDKs

  • Browser SDK
  • Server helper

Guides

  • Client tokens
  • Verify sessions
  • Rate limiting
  • Uptime & status

API

  • API basics
  • HTTP routes

~2 min read

HTTP routes

Reference table for the HTTP API. Most custom sites only need the client/* routes from your server with the project secret.

Start here

With the server helper or your own HTTP client, call these from your backend — not from the browser:

MethodPathAuthNotes
GET/projects/client/extra-metadatanoneProject secret or client JWT
PATCH/projects/client/extra-metadatanoneProject secret or client JWT
GET/projects/client/session-verifynoneCheck verify session: query projectId + Bearer project secret + Cookie (defaults qyzar_session_token, qyzar_session_id). See docs/session-verification.
POST/projects/client/session-verifynoneSame as GET; body may include sessionId, sessionToken or rely on cookies forwarded from the browser.
POST/projects/client/tokennoneMint browser client JWT: body.projectId + project secret. Optional sessionId + sessionToken (or Cookie) binds JWT expiry to the connect session. Optional metadata: identifier, email, phone, nested JSON.
GET/projects/client/token-verifynoneVerify client JWT: query projectId + clientToken (or X-Qyzar-Client-Token / Bearer) + project secret. Returns valid, sessionId (when bound), and public metadata.
POST/projects/client/token-verifynoneSame as GET; body projectId + clientToken.

All routes

Show full list (56 routes)
MethodPathAuthNotes
POST/auth/2fa/createnone—
POST/auth/2fa/recoverynone—
POST/auth/2fa/verifynone—
GET/auth/meuserReturns passwordAuth when the account uses email/password (not Google-only).
PATCH/auth/passworduser—
POST/auth/password-reset-confirmnone—
POST/auth/password-reset-requestnone—
POST/auth/registernone—
POST/auth/signinnone—
POST/auth/verify-emailnone—
POST/auth/verify-email/resendnone—
POST/billing/checkoutuserBody: planKey pro|enterprise; optional successUrl, cancelUrl. Server maps to STRIPE_PRICE_* env. Returns Checkout Session url.
GET/billing/plansuserPlan catalog: monthlyPriceCents, stripePriceId when configured; checkoutAvailable per tier.
POST/billing/portaluserBody: optional returnUrl. Stripe Customer Portal url.
GET/billing/statususerconfigured + hasCustomer when STRIPE_SECRET_KEY is set.
PATCH/billing/subscriptionuserBody: subscriptionId, newPriceId (must match STRIPE_PRICE_PRO or STRIPE_PRICE_ENTERPRISE); optional prorationBehavior.
POST/billing/subscription/canceluserBody: subscriptionId; optional immediately (default false = cancel at period end).
POST/billing/subscription/resumeuserBody: subscriptionId; clears cancel_at_period_end.
GET/billing/subscriptionsuserLists Stripe subscriptions for the signed-in user.
POST/connect/reverifynoneSession JWT + entropy payload
GET/opt-out/confirmnone—
POST/origin-tokensuser—
POST/origin-tokens/invalidateuser—
GET/origin-tokens/statusnone—
POST/origin-tokens/verifynone—
GET/pingnone—
DELETE/projectsuser—
GET/projectsuser—
PATCH/projectsuser—
POST/projectsuser—
GET/projects/analyticsusersection=clusters|devices|browsers|sessions|traffic (Postgres traffic: region + platform)
GET/projects/browser-datauser—
POST/projects/client/ato-add-identifiernoneAnti-ATO: append trusted identifier to device metadata
POST/projects/client/ato-login-attemptnoneAnti-ATO: project secret; logs attempt, returns prior snapshot + score + lastLoginAt
POST/projects/client/rate-limit-checknoneProject secret; IP + optional metadata buckets; optional settingsOverride and analytics on deny
GET/projects/dashboard-summaryuser—
GET/projects/detailuser—
GET/projects/devices-datauser—
GET/projects/entropy-snapshotuser—
GET/projects/extra-metadatauser—
PATCH/projects/extra-metadatauser—
GET/projects/overview-statsuser—
POST/projects/rate-limit/checkuser—
POST/projects/secret/2fauser—
POST/projects/secret/revealuser—
GET/projects/settingsuser—
PATCH/projects/settingsuser—
POST/stripe/webhooknoneStripe-signed webhook; raw JSON body. Persists billing_event_logs.
POST/test/captchanoneDev / test captcha tooling

Auth types are summarized in API basics. Dashboard routes use your Qyzar login; /projects/client/* uses the project secret.