> 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/managing-apps-and-credentials.md). # Managing applications and credentials An **application** represents a consumer's integration. It carries the credentials the gateway validates on every call and holds the subscriptions that grant it access to APIs. A consumer works in this area whenever they need to create an integration, retrieve or rotate a secret, or check which APIs an application can reach. ![Figure 1. The My Apps area, where a consumer manages their applications.](/files/mlA1w355qPiWsv1ByahJ) ### What you see A signed-in consumer reaches their applications from the account menu in the top-right, under **My Apps**. * **Profile header**: the consumer's name and account details, with **View Profile** and **Edit Profile** controls to update contact information. * **Tabs**: **View Profile**, **Edit Profile**, **My Apps**, and **Analytics** organise the account area. **My Apps** is the default working tab. * **App counters**: three summary tiles, **Total**, **Active**, and **Inactive**, give an at-a-glance picture of how many applications exist and how many are currently enabled. * **Application list**: each application shows its name and a link through to its detail, where credentials and subscriptions live. * **Empty state**: a fresh account shows **No apps yet** with a **Browse API Catalog** call to action, since an application is created as part of subscribing to an API. The account screen below shows the profile and tab layout that surrounds the app list. ![Figure 2. The consumer account screen with profile and tabs.](/files/ikBeZvBY7M4NrQI23r30) ### Creating an application An application is created through the subscription flow, not from a standalone form: 1. Open **My Apps** from your account menu, or click **Browse API Catalog** from the empty state. 2. Choose the API or Product to subscribe to and start the subscription flow. 3. When prompted, create an application: give it a name and, where offered, a description and environment. 4. Save. The portal creates the application, records the subscription against it, and issues the application's credentials. {% hint style="info" %} **Note:** Where the provider requires approval, the new subscription starts in a pending state and becomes active only after the provider approves it. {% endhint %} ### Working with credentials Each application carries two values issued by the portal: a **client identifier** and a **client secret**. From an application's detail a consumer can: 1. View the credentials and copy the client identifier. 2. Reveal and copy the client secret at issue time. 3. Rotate the secret, which generates a replacement and invalidates the old value. 4. Review which APIs and Products the application is subscribed to, and the state of each subscription. 5. Read per-application activity under the **Analytics** tab, where the portal exposes it. The application sends the client identifier and client secret with every request to a subscribed API. The gateway, not the portal, validates them on each call: the portal is a management surface for issuing and rotating credentials, not a proxy in the request path. ### Verify * The new application appears in the **My Apps** list and the **Total** counter increases. * The application shows the expected subscription, and the **Active** counter reflects it once any required approval clears. * A test call to the subscribed API using the issued client identifier and client secret returns a valid response from the gateway. ### Options and variations * **Subscription states**: a subscription may be pending (awaiting approval), active (callable), or suspended (access withdrawn). A pending subscription does not yet permit calls. * **Credential rotation**: rotating the secret takes effect immediately at the gateway, so update the running integration with the new value before retiring the old one. * **Counters**: an application with no active subscriptions, or one that has been disabled, counts toward **Inactive** rather than **Active**. {% hint style="warning" %} **Caution:** A client secret is shown so it can be copied at issue or rotation time. Treat it as sensitive, store it securely, and rotate it promptly if it is exposed. {% endhint %} {% hint style="success" %} **Result:** The consumer has an application with valid credentials, subscribed to the APIs they need, and can rotate those credentials whenever required. {% 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/managing-apps-and-credentials.md?ask=&goal= ``` `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.