# Getting Started

## Prepare base URL

The Verifier API environment is fully managed by TNG's Product Suite Platform (PSP), eliminating the need for you to set up or maintain the underlying technology stack. You will be provided with the **Verifier API Base URL** specific to your environment. The API utilizes a single, standardized base URL for all endpoints, ensuring consistency and simplicity in integration.

```bash
$API_KEY=INSERT_YOUR_API_KEY_HERE # the API key assigned to you via Issuer portal
$IDENTITY_ENV_HASH=426f1ce15bf3df70 # the unique hash idenitifer for your env
$VERIFIER_API_BASE_URL=https://identity.products.teranode.group/products/web/$IDENTITY_ENV_HASH/verifier
```

{% hint style="info" %}
To check if your Verifier API Base URL is valid, you can visit the Ping-Pong website at <mark style="color:blue;">GET</mark> <mark style="color:blue;"></mark><mark style="color:blue;">`$VERIFIER_API_BASE_URL/api/v1/ping`</mark>
{% endhint %}

## Authentication

The API supports API Key authentication providing the following header

```
x-api-key: <API_KEY>
```

The API key grants you access to the API documented at [API Documentation](/tng-identity-documentation/tng-identity-issuers/issuer-api/api-documentation.md)

If the API returns 403 means the API key privileges does not suffice to access the action you want to perform. Ask an Admin or Owner of the environment to review your access.

If the API returns 401 means the API key is not authorised or invalid. Ask an Admin or Owner to review access.

## Authorization

Same as the whole Identity suite, the Verifier API uses role-based access control (RBAC) to manage permissions. Authorization is enforced using the `cognito:groups` claim in the JWT access token, which specifies the user’s assigned claims. These permissions determine what actions the user can perform within the API.

### Supported Roles

* **Verifier Admin - c**an verify verifiable credentials, can view all the verifiable credentials that have been verified based on the pre-defined list of schemas & more
* **Verifier User** - can verify verifiable credentials, can view its own verified credentials ,can view its own verifiable credentials that have been verified based on the pre-defined list of schemas & more
* **Verifier Auditor -** can view the history verified credentials & more


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.teranode.group/tng-identity-documentation/tng-identity-verifier/verifier-api/getting-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.