> For the complete documentation index, see [llms.txt](https://docs.humanity.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.humanity.org/developer-portal.md).

# Developer Portal

Access the Humanity developer dashboard to create applications, generate API credentials, configure OAuth settings, and manage integrations. Available for sandbox and production.

{% embed url="<https://drive.google.com/file/d/1ivrI9HX950bq2EzZfqezQW3hk343YlTF/preview>" %}

The Developer Portal is where you register your application and get the credentials needed to integrate with Humanity. It takes about 5 minutes to set up.

***

### Step 1 — Sign up or log in

<a href="https://developers.humanity.org/" class="button primary" data-icon="arrow-up-right-from-square">Go to Developer Portal</a>

***

### Step 2 — Create an application

Once logged in:

1. Click **\[Create App / New Application]**
2. Enter your application name

<figure><img src="https://383350980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL1EBectYBMnvu9vU5N1M%2Fuploads%2FSz9GfEVtS984Do7IMNPC%2FScreenshot%20From%202026-03-30%2011-54-37.png?alt=media&amp;token=4cc4249d-1ed8-463a-8867-0f2abfe45dc5" alt=""><figcaption></figcaption></figure>

***

### Step 3 — Review and Save your credentials

After creating your application, credentials both for sandbox and production are created. make sure you download them or copy / pasted into your `.env` file or a save place.

<figure><img src="https://383350980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL1EBectYBMnvu9vU5N1M%2Fuploads%2FzGO4E37nrCaOtV3sIIa3%2FDevPortalEnv.png?alt=media&amp;token=74f59e58-46bc-422c-9db0-ecb3413321d9" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Never expose these credentials in client-side code or commit them to version control. Store them in environment variables or your platform's secret manager.
{% endhint %}

***

### Step 4 — Add your URI + select your presets / configure scopes

**Select the environment** you want to work with and under ***Settings*** add you URI and your presets + scopes then save your changes.

Presets define what your app is allowed to verify about a user — for example, `is_human`, `is_21_plus`, or KYC status.

You can learn more about scopes and presets here [SDK OAuth Scopes and Presets](https://docs.humanity.org/build-with-humanity/build-with-the-sdk-api/sdk-oauth-scopes-and-presets.md)

For the example below we targeting s**andbox** environment and adding a ***Redirect URI*** and the following **scopes:**

* `identity:read`
* `profile.full`
* `openid`
* `data.read`

<figure><img src="https://383350980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL1EBectYBMnvu9vU5N1M%2Fuploads%2FZJJlgXcLTWBh9f8AgoAS%2FExample_DevPortal%201.png?alt=media&amp;token=6b3cf031-66ad-4de0-b58f-3683f6651016" alt=""><figcaption></figcaption></figure>

For **sandbox testing**, you can generate mock preset data from the [Sandbox Dashboard](https://app.sandbox.humanity.org/sandbox) without needing a real verified user.&#x20;

Learn more here [Generating Mock Credentials](https://docs.humanity.org/developer-guides-and-tutorials/generating-mock-credentials.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.humanity.org/developer-portal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
