---
title: "Verify Push Challenge"
method: POST
path: "/verify/push"
tags: ["Push"]
---

# Verify Push Challenge

`POST /verify/push`

Verify a challenge to a user's mobile device. Use this endpoint from the app which initiated the challenge to determine if the user approved or rejected the request (e.g. via polling).

## Request body

- object
  - `challengeId` string, required — The challenge ID returned when starting the push challenge.

## Response `200`

OK

- object
  - `isVerified` boolean, required — True if the user approved the auth request on their mobile device. False if they rejected the request.
  - `isConsumed` boolean, required — True if the user has either approved or rejected the auth request. False if they have not yet responded to the request.
  - `accessToken` string — A new short-term token with scopes to manage authenticators (e.g. add secondary authenticators, remove authenticators, view or regenerate recovery codes). Only present if the challenge succeeded.

## Other responses

- `400` — Invalid Request
- `401` — Unauthorized
- `404` — Not Found

---

[API](https://skmtc.net/authsignal/apis/call-connect-api.md) · [All operations](https://skmtc.net/authsignal/apis/call-connect-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/authsignal/call-connect-api/versions/5604d744e3ad/schema)