> 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/getting-started.md).

# Getting started

This is the fastest path from landing on the portal to making your first authenticated API call. Each step links to the page that covers it in depth, so use this as the map and follow the detail where you need it.

![Figure. The API catalog, the starting point for every consumer journey.](/files/5WI8cNKrEfx3nyRMCa1m)

### The five-step path

1. **Find an API.** Open the catalog, search or filter by domain, and open an API or Product that fits your use case. See [Browsing the catalog](/developer-portal/discover-apis/discovering-apis.md).
2. **Evaluate it.** Read the Overview, Documentation, and Specification tabs to confirm the endpoints, authentication, and data you need. See [Exploring an API](/developer-portal/discover-apis/exploring-an-api.md).
3. **Sign up and sign in.** Create a consumer account or sign in, so you can subscribe and hold credentials. See [Signing up and signing in](/developer-portal/subscribe-and-get-access/signing-up-and-signing-in.md).
4. **Create an application and subscribe.** Create an application, subscribe it to the API or Product, and collect the **Application Credentials** the gateway checks on every call. See [Subscribing to APIs and Products](/developer-portal/subscribe-and-get-access/requesting-a-subscription.md) and [Managing applications and credentials](/developer-portal/subscribe-and-get-access/managing-apps-and-credentials.md).
5. **Call and track.** Send your first request, then watch usage build up. See [Testing an API](/developer-portal/test-and-track-usage/testing-an-api.md) and [App analytics and usage](/developer-portal/test-and-track-usage/app-analytics.md).

### What you need

* **An email address** for the consumer account, or your organisation's single sign-on.
* **An application** to carry credentials. One application can subscribe to several APIs and Products.
* **The credentials** issued on subscription: a key or client identifier and secret, sent on every request to the gateway.

{% hint style="info" %}
The portal is a management surface, not part of the request path. Your application calls the gateway directly with its issued credentials; the gateway validates them and enforces the plan's quota and rate limits.
{% endhint %}

### Where to go next

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Discover APIs</strong></td><td>Browse the catalog and evaluate an API across its tabs.</td><td><a href="/pages/8uzCNyupQmOHhjw6ijWV">/pages/8uzCNyupQmOHhjw6ijWV</a></td></tr><tr><td><strong>Subscribe and get access</strong></td><td>Sign up, create an application, subscribe, and collect credentials.</td><td><a href="/pages/LCqosmfOs5UlFxQFpspG">/pages/LCqosmfOs5UlFxQFpspG</a></td></tr><tr><td><strong>Test and track</strong></td><td>Send requests and watch usage and analytics build up.</td><td><a href="/pages/OagKRTOfCUvYNByO6aAL">/pages/OagKRTOfCUvYNByO6aAL</a></td></tr></tbody></table>


---

# 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/getting-started.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.