---
title: "Number verify device authorization"
method: GET
path: "/camara/number-verification/v0/authorize"
tags: ["connectivity", "camara", "network-based-number-verification"]
---

# Number verify device authorization

`GET /camara/number-verification/v0/authorize`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/camara/number-verification/v0/authorize`
- Auth: none declared

Use this method to redirect the mobile device on the MNO network for authorization, based on the mobile device IP address.
Upon authorization, the device is redirected back to the URL specified in `redirectUrl`.
When redirected back, a new query parameter `code` is being added.
It needs to be sent in a subsequent verify request to complete verification.

**Error handling behavior:**
- When `redirectUrl` parameter **is provided**: All errors are returned as a 302 redirect back to the `redirectUrl` with OAuth 2.0 error query parameters (`error`, `error_description` (optional), `state`).
- When `redirectUrl` parameter **is NOT provided**: A JSON response is returned (see below).

## Query parameters

- `clientId` string, required
- `redirectUrl` string, uri, required
- `state` string
- `login_hint` string

## Other responses

- `302`: Redirect to MNO authorization endpoint. Response body is empty, information is returned in response headers.
- `400`: Bad request. When `redirectUrl` is available, this error is returned via 302 redirect with `error=invalid_request`
- `401`: Unauthenticated
- `500`: Internal server error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)