> 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/discover-apis/discovering-apis.md).

# Discovering APIs

The developer portal is the public, branded surface your external consumers use to find and adopt your APIs. This page describes what a consumer or public visitor sees the moment they arrive and how they move from the home page into the catalog. Everything described here is reachable without an account; signing in unlocks subscriptions and applications, covered in the chapters that follow.

![Figure 1. The developer portal landing page that public visitors see first.](/files/fBiwJwvJYeq0Az7mF9y6)

### What you see

* **Landing page**: the brand, a short value statement, and entry points into the catalog, documentation, guides, and support. The logo, accent colour, and navigation reflect your organisation's branding, all configured on the provider side.
* **Top navigation**: persistent links to APIs, Products, documentation, and support, plus a sign-in control. A signed-out visitor sees the public set; signing in adds account areas such as apps and subscriptions.
* **API Discovery catalog**: the **APIs** area, titled **API Discovery**, lists every API published to the portal as a grid of cards. Each card shows the API name, a short description, a category or domain tag, and a **View API** link.
* **Search box**: a **Search APIs** field that matches on name and keyword, with a **Search** button to run the query.
* **Filters**: a control to narrow the list by attributes such as **Domain** or category, so a consumer can scope a large catalog to the area they care about.
* **Grid / list toggle**: a layout switch on the right that swaps between a card grid and a denser list view.
* **Product Discovery**: a separate **Products** area listing subscribable **API Products**, curated bundles that group related APIs under a single offering with its own plan and terms.

![Figure 2. The API Discovery catalog, where consumers browse every published API.](/files/5WI8cNKrEfx3nyRMCa1m)

### Find an API or Product

1. Open **APIs** from the top navigation. The catalog opens at the API Discovery page.
2. Type a name or keyword into the **Search APIs** box and click **Search** to filter the cards.
3. Narrow the results with the **Filters** control, for example by **Domain** or category.
4. Switch between grid and list views with the layout toggle on the right to suit how you scan.
5. Click **View API** on any card to open its detail page.
6. To browse bundles instead, open **Products** and review what a Product includes before subscribing.

### Verify

* The catalog returns at least one card matching your search term, and clearing the search restores the full list.
* Applying a Domain or category filter reduces the grid to matching APIs only.
* **View API** opens the detail page for the card you clicked, covered in the next chapter.

{% hint style="success" %}
**Tip:** Categories and tags come from the metadata a provider completes when publishing, so well-tagged APIs are far easier for consumers to find.
{% endhint %}

{% hint style="info" %}
**Note:** The catalog shows only what a provider has published and made visible. An anonymous visitor and a signed-in consumer may see different sets if some APIs are restricted to authenticated or approved audiences.
{% endhint %}

### Options and variations

* **Public vs signed-in view**: anonymous visitors can browse, search, and read; subscribing and creating apps require signing in.
* **Visibility**: APIs and Products can be public, restricted to signed-in consumers, or limited to specific audiences, so the catalog a given visitor sees depends on their access.
* **APIs vs Products**: individual APIs are explored and, where allowed, tested directly; Products are the subscribable unit that carries a plan and terms.

{% hint style="success" %}
**Result:** A visitor can locate any published API or Product by search, filter, or category, then open it to learn more before deciding whether to sign in and subscribe.
{% 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/discover-apis/discovering-apis.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.