> For the complete documentation index, see [llms.txt](https://docs.digitalapi.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalapi.ai/developer-portal/subscribe-and-get-access/signing-up-and-signing-in.md).

# Signing up and signing in

Browsing the catalog and reading documentation are open to everyone. The moment a consumer wants to subscribe to an API, create an application, or obtain credentials, the portal asks them to authenticate. Signing up creates the developer account that owns those applications and subscriptions; signing in returns to that same account on later visits.

![Figure 1. The get-started page that orients a new consumer.](/files/9rf8Nl74t7vLkFMx8tuE)

### What you see

* **Get started page**: a landing surface that explains what the portal offers and points to the two next steps, registration and the catalog. It sets expectations before any form is shown.
* **Sign up link and Login link**: paired controls in the top-right of every page. Sign up opens the registration form; Login opens the credentials form.
* **Sign up form**: the registration fields the provider has configured. A typical form asks for first and last name, a work email, a username, and a password with a confirmation field. Some deployments add an organisation or company field and a terms-acceptance checkbox.
* **Login form**: an email or username field, a password field, and a submit button. Where the provider has configured an identity provider, a single sign-on button appears alongside or in place of the password fields.
* **Account menu**: after authentication, the top-right shows the signed-in account with links to applications, subscriptions, and profile settings.

### Create an account

![Figure 2. The consumer sign-up registration form.](/files/NvuBZF1ODbVChqlAW0DQ)

1. Click **Sign up** in the top-right of any portal page.
2. Complete the registration form. Provide your name, a valid email, a username, and a password that meets the strength rules shown.
3. Accept the terms if a checkbox is presented.
4. Submit the form.
5. Complete any email verification step: open the message sent to your address and follow its confirmation link.

{% hint style="info" %}
**Note:** Registration fields and whether new accounts need approval are set by the provider, so the exact form varies between deployments.
{% endhint %}

### Sign in

1. Click **Login** in the top-right of any portal page.
2. Enter your email or username and your password, or choose the single sign-on option if it is offered.
3. Submit. You return to the portal with the account menu available in the top-right.

### Verify

* The top-right shows your account name or avatar rather than the Sign up and Login links.
* Opening the applications area loads your account. A brand-new account shows an empty state with no applications and no subscriptions yet, which is expected.
* If a verification email has not arrived, check spam and request a resend from the login page before contacting support.

### Options and variations

* **Open self-registration**: some providers let any visitor register and use the portal right away, with only email verification in the path.
* **Approval-gated accounts**: other providers hold a new account for review. In that case the account exists after sign-up but stays inactive until a provider approves it, and certain actions such as subscribing remain unavailable in the meantime.
* **Single sign-on**: where an identity provider is wired in, the portal delegates authentication to it. The consumer never sets a portal password; the account is provisioned from the identity provider on first login.
* **Public versus signed-in view**: anonymous visitors see the catalog, documentation, and the get-started page. Subscription buttons, application management, and credentials appear only after a consumer signs in.

{% hint style="success" %}
**Result:** The consumer has a verified developer account and an active session, and can now subscribe to APIs and create applications.
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://docs.digitalapi.ai/developer-portal/subscribe-and-get-access/signing-up-and-signing-in.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.