---
title: "Check Silent Authentication"
method: POST
path: "/network/silent-auth/{requestId}/check"
tags: ["network > silentAuth"]
---

# Check Silent Authentication

`POST /network/silent-auth/{requestId}/check`

## Request

- Base URL: `https://api.pinnacle.sh`
- URL: `https://api.pinnacle.sh/network/silent-auth/{requestId}/check`
- Auth: API key in header `PINNACLE-API-KEY`

Complete a Silent Authentication request by exchanging the code returned from the JSON flow. Call this from your server after the user's mobile app fetches `jsonUrl`.

This endpoint returns a terminal verification result. To inspect pending lifecycle states such as `started` or `challenge-issued`, use [Get Network Request](/api-reference/network/get-network-request).

<Note>
  Limited availability. Contact [founders@pinnacle.sh](mailto:founders@pinnacle.sh) to request access.
</Note>

## Path parameters

- `requestId` string, required: Unique Pinnacle ID for a Network API request.

## Request body

- SilentAuthCheckRequest
  - `code` string, required: Code returned by the JSON Silent Auth device flow.

## Response `200`

Returns the terminal verification status.

- SilentAuthCheckResponse
  - `requestId` string, required: Unique Pinnacle ID for a Network API request.
  - `status` 'completed' | 'failed', required: Terminal verification result after exchanging a device flow code. `completed` means the phone number was verified; `failed` means the verification did not complete successfully. To inspect pending lifecycle states, use [Get Network Request](/api-reference/network/get-network-request).

## Other responses

- `400`: The request was unacceptable, often due to providing an invalid update. <br> Errors may originate from invalid payload or from Pinnacle's additional validation checks. For example, providing an URL that cannot be accessed, updating a campaign that is currently being reviewed, updating data that you cannot access, sending a malformed message, and so on. <br> For `Pinnacle Validation Error` inspect the `error` payload to determine the source of the failure. These errors are likely due to additional validation and business logic checks.<br> For `Request Validation Error` inspect the `description` and `errors` payload to determine the source of failure. These errors are likely due to invalid payload inside the request.
- `401`: The request lacks valid authentication credentials or the provided credentials are invalid. <br> Ensure you're including a valid API key in the request headers and that your account has the necessary permissions to access this endpoint.
- `403`: Your subscription does not include access to this feature. <br> This occurs when attempting to use functionality that requires a higher subscription tier. Please upgrade your subscription to access this feature.
- `500`: An unexpected error occurred on Pinnacle's servers while processing your request. <br> If this error persists, please contact support with the request details.

---

[API](https://skmtc.dev/pinnacle/apis/pinnacle-2.md) - [All operations](https://skmtc.dev/pinnacle/apis/pinnacle-2/llms.txt) - [OpenAPI document](https://skmtc.dev/pinnacle/apis/pinnacle-2/revisions/45416dadab79?raw)