MANSOQ Knowledge
← This release collection

IT & Integrations · VERSION 912828b3

Read token verification without confusing it with access

Read the required token input and exact empty-object success while keeping cryptographic verification separate from current access.

IT administrator · Integration engineer · Developer

The verify operation explicitly limits its result: untyped token validation does not establish current account/facility access, MFA completion or custom logout-cache state. Request Schema requires one write-only token string.123
Recorded release 912828b3 · 2026-10-19 · 1728 × 921

Read untyped verification’s boundary

Capture details

Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. The verify operation explicitly limits its result: untyped token validation does not establish current account/facility access, MFA completion or custom logout-cache state. Request Schema requires one write-only token string.

Image SHA-256 4dffa431af2a4d606fbd6e676e195d526e8b71cdedf7b0d15957af71d70f4db7

  1. Exact verification path: Confirm the verify operation rather than refresh.
  2. Limited meaning: Read the full limitation before interpreting an empty successful result.
  3. Required token input: The schema contains a type and required marker, not a secret.
HTTP 200 Schema is an object with no defined properties and additional properties forbidden. The required token input is visible above. It does not return a token pair or permission record.123
Recorded release 912828b3 · 2026-10-19 · 1728 × 921

Read exact empty-object verification success

Capture details

Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. HTTP 200 Schema is an object with no defined properties and additional properties forbidden. The required token input is visible above. It does not return a token pair or permission record.

Image SHA-256 e250b8243e6ea7c51e8b23ea6a0e2f61de099154106bf7543caab61d1eb1dcf8

  1. Write-only token: Use the exact documented input name.
  2. HTTP 200 schema: This is the successful response definition.
  3. No additional properties: The successful JSON object is exactly empty; no access or refresh field is returned.

6 of 6 content blocks have reviewed image alignment. Missing overview or prerequisite images remain open.

Before you begin

  • Use the reference for release 912828b3. Its source receipt and schema fingerprint identify this local documentation export; the API label and schema dialect are separate.
    The genuine privacy-minimized local documentation receipt shows full release 912828b3 commit/tree, OpenAPI 3.1, its schema fingerprint, 900 paths, 1,227 operations, 687 schema components and verified read-only zero-query rendering. It contains no local filesystem path.1234567
    Recorded release 912828b3 · 2026-10-19 · 1728 × 921

    Compare the exact documentation source

    Capture details

    Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. The genuine privacy-minimized local documentation receipt shows full release 912828b3 commit/tree, OpenAPI 3.1, its schema fingerprint, 900 paths, 1,227 operations, 687 schema components and verified read-only zero-query rendering. It contains no local filesystem path.

    Image SHA-256 99de6c8b2ce55151bb26d366204657af1b66c26e48742b8502ba5f5b60bd54a2

    1. Full committed release: Compare the exact sourceCommit, not only a short label.
    2. Source tree: This is the retained committed Git tree.
    3. Exact schema fingerprint: Compare the complete SHA256 with the selected schema artifact.
    4. Read-only viewer: This describes documentation browsing, not request execution.
    5. Verified source count: All 1,817 core source blobs were checked against this release.
    6. Zero data queries: The documentation export did not query application data.
    7. Bounded scope: Endpoint execution, tenant compatibility and production deployment need separate evidence.
    The installed read-only Swagger reader shows the separate API 1.0.0 and OAS 3.1 labels and the auth operation group. Logout has a security marker; refresh and verify are separate paths. No credentials were entered.1234567
    Recorded release 912828b3 · 2026-10-19 · 1728 × 921

    Find the three auth operations safely

    Capture details

    Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. The installed read-only Swagger reader shows the separate API 1.0.0 and OAS 3.1 labels and the auth operation group. Logout has a security marker; refresh and verify are separate paths. No credentials were entered.

    Image SHA-256 b3a5df58e18c5f9c47e13754d34a9c3a500c21ce9cba800d21c786967d28f23a

    1. Requests disabled: The reference banner states that requests are disabled.
    2. API label and dialect: API 1.0.0 and OAS 3.1 are separate from the Git release in the source receipt.
    3. Filter the auth group: Use the group filter to locate authentication contracts.
    4. Authenticated logout: Read this path separately from refresh and verify.
    5. Security requirement: The lock indicates that the logout operation declares authentication, not that this viewer has signed in.
    6. Refresh contract: Read the required input and rotation-specific response here.
    7. Verification contract: Read the limited token-validation contract here.
  • The reference is read-only. These frames show contract types and examples, not credentials or live request results. Actual calls and deployment-specific authorization require their own verified workflow.
    The installed read-only Swagger reader shows the separate API 1.0.0 and OAS 3.1 labels and the auth operation group. Logout has a security marker; refresh and verify are separate paths. No credentials were entered.1234567
    Recorded release 912828b3 · 2026-10-19 · 1728 × 921

    Find the three auth operations safely

    Capture details

    Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. The installed read-only Swagger reader shows the separate API 1.0.0 and OAS 3.1 labels and the auth operation group. Logout has a security marker; refresh and verify are separate paths. No credentials were entered.

    Image SHA-256 b3a5df58e18c5f9c47e13754d34a9c3a500c21ce9cba800d21c786967d28f23a

    1. Requests disabled: The reference banner states that requests are disabled.
    2. API label and dialect: API 1.0.0 and OAS 3.1 are separate from the Git release in the source receipt.
    3. Filter the auth group: Use the group filter to locate authentication contracts.
    4. Authenticated logout: Read this path separately from refresh and verify.
    5. Security requirement: The lock indicates that the logout operation declares authentication, not that this viewer has signed in.
    6. Refresh contract: Read the required input and rotation-specific response here.
    7. Verification contract: Read the limited token-validation contract here.
    The verify operation explicitly limits its result: untyped token validation does not establish current account/facility access, MFA completion or custom logout-cache state. Request Schema requires one write-only token string.123
    Recorded release 912828b3 · 2026-10-19 · 1728 × 921

    Read untyped verification’s boundary

    Capture details

    Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. The verify operation explicitly limits its result: untyped token validation does not establish current account/facility access, MFA completion or custom logout-cache state. Request Schema requires one write-only token string.

    Image SHA-256 4dffa431af2a4d606fbd6e676e195d526e8b71cdedf7b0d15957af71d70f4db7

    1. Exact verification path: Confirm the verify operation rather than refresh.
    2. Limited meaning: Read the full limitation before interpreting an empty successful result.
    3. Required token input: The schema contains a type and required marker, not a secret.
    HTTP 200 Schema is an object with no defined properties and additional properties forbidden. The required token input is visible above. It does not return a token pair or permission record.123
    Recorded release 912828b3 · 2026-10-19 · 1728 × 921

    Read exact empty-object verification success

    Capture details

    Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. HTTP 200 Schema is an object with no defined properties and additional properties forbidden. The required token input is visible above. It does not return a token pair or permission record.

    Image SHA-256 e250b8243e6ea7c51e8b23ea6a0e2f61de099154106bf7543caab61d1eb1dcf8

    1. Write-only token: Use the exact documented input name.
    2. HTTP 200 schema: This is the successful response definition.
    3. No additional properties: The successful JSON object is exactly empty; no access or refresh field is returned.

1. Read the token input and exact success

Open POST /api/v1/auth/token/verify/. Request Schema requires one write-only token string. Response 200 is an empty JSON object. It is not an access/refresh pair, a user profile or a facility permission result. These screenshots show schema definitions and placeholders.

The verify operation explicitly limits its result: untyped token validation does not establish current account/facility access, MFA completion or custom logout-cache state. Request Schema requires one write-only token string.123
Recorded release 912828b3 · 2026-10-19 · 1728 × 921

Read untyped verification’s boundary

Capture details

Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. The verify operation explicitly limits its result: untyped token validation does not establish current account/facility access, MFA completion or custom logout-cache state. Request Schema requires one write-only token string.

Image SHA-256 4dffa431af2a4d606fbd6e676e195d526e8b71cdedf7b0d15957af71d70f4db7

  1. Exact verification path: Confirm the verify operation rather than refresh.
  2. Limited meaning: Read the full limitation before interpreting an empty successful result.
  3. Required token input: The schema contains a type and required marker, not a secret.
HTTP 200 Schema is an object with no defined properties and additional properties forbidden. The required token input is visible above. It does not return a token pair or permission record.123
Recorded release 912828b3 · 2026-10-19 · 1728 × 921

Read exact empty-object verification success

Capture details

Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. HTTP 200 Schema is an object with no defined properties and additional properties forbidden. The required token input is visible above. It does not return a token pair or permission record.

Image SHA-256 e250b8243e6ea7c51e8b23ea6a0e2f61de099154106bf7543caab61d1eb1dcf8

  1. Write-only token: Use the exact documented input name.
  2. HTTP 200 schema: This is the successful response definition.
  3. No additional properties: The successful JSON object is exactly empty; no access or refresh field is returned.

2. Read the documented refusal shapes

Expand HTTP 400 and 401. Required-field or parser failures and signed-token errors have different documented shapes. Handle the response status and actual JSON deliberately; an empty successful object should not be replaced with an invented payload.

The 400 schema alternatives show token/non_field_errors arrays or required detail. The 401 schema requires detail and code. These contract definitions are separate from a live access check.12345
Recorded release 912828b3 · 2026-10-19 · 1728 × 921

Read verification’s input and signed-token errors

Capture details

Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. The 400 schema alternatives show token/non_field_errors arrays or required detail. The 401 schema requires detail and code. These contract definitions are separate from a live access check.

Image SHA-256 d0877e7621e28ce2bd8b6aaeec85b16d0ea27cba8f6ba2e2e99ffa7f216dacf4

  1. Required-input failure: Read the 400 alternatives deliberately.
  2. Token error array: At least one field error property is required in this alternative.
  3. Detail alternative: Parser failures can use the required detail object.
  4. Signed-token error: Read HTTP 401 separately from input validation.
  5. Required error code: The signed-token error requires a code string alongside detail.

3. Keep verification separate from authorization and logout state

Read the operation description. Untyped verification does not establish fitness for a use, current account/facility access, MFA completion or custom logout-cache state. A separate normal local check observed verify returning an empty object for a logged-out access token while the protected current-user endpoint refused it. That bounded result does not authorize reuse of the token or establish a tenant grant.

The verify operation explicitly limits its result: untyped token validation does not establish current account/facility access, MFA completion or custom logout-cache state. Request Schema requires one write-only token string.123
Recorded release 912828b3 · 2026-10-19 · 1728 × 921

Read untyped verification’s boundary

Capture details

Fresh genuine 1728×921 Chrome capture of the exact committed 912828b3 read-only API reference. No credentials were entered or endpoint requests submitted. The verify operation explicitly limits its result: untyped token validation does not establish current account/facility access, MFA completion or custom logout-cache state. Request Schema requires one write-only token string.

Image SHA-256 4dffa431af2a4d606fbd6e676e195d526e8b71cdedf7b0d15957af71d70f4db7

  1. Exact verification path: Confirm the verify operation rather than refresh.
  2. Limited meaning: Read the full limitation before interpreting an empty successful result.
  3. Required token input: The schema contains a type and required marker, not a secret.

Source evidence

Every citation uses this exact committed version. The private source repository requires access.