> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer Access: Managing API Keys

> Reference for the Developer Access tab in DualEntry Organization Settings: the API key table columns, creating a key, and revoking a key.

The **Developer Access** tab of Organization Settings manages API keys for programmatic access to your DualEntry organization. API keys authenticate external applications and integrations. Only the Admin role can open this tab.

To reach this tab, navigate to **Settings → Developer Access**, accessible from your organization's name in the top left corner of the screen.

The tab has two sub-tabs: **API Keys** and **Webhooks**, which lets you create and manage webhooks directly in the UI, not just via the API. This page covers only API Keys; for the event catalog, payload format, and signature verification, see [Webhooks](/accountants/integrations/webhooks).

A key carries roles of its own, chosen when you create it, and is not tied to the user who created it. For the procedure, including how to choose those roles and hand the key over safely, see [How to Give an Integration Access to DualEntry](/developers/guides/how-to-give-an-integration-access).

## API key table

Columns in the API key table on the Developer Access tab:

| Column        | Description                                                                                                                                                                         |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Label**     | A descriptive name for the key (e.g., the app or person it was created for). Unique within the organization                                                                         |
| **API Key**   | The masked key, shown as prefix, asterisks, and the last four characters (for example `org_production_18e3****cSk8`). The full secret is displayed once at creation and never again |
| **Roles**     | The permission role(s) assigned to this key (e.g., Admin). A key with no roles authenticates but is refused by every endpoint                                                       |
| **Status**    | `Active`: valid and usable. `Revoked`: disabled and rejected on all API calls. Revocation cannot be undone                                                                          |
| **Last Used** | Most recent date the key authenticated a request. Written asynchronously and shown as a date, not a time                                                                            |
| **Created**   | Date the key was generated                                                                                                                                                          |

The **⋮** menu on each row offers **Edit**, which changes the key's name and roles without invalidating the secret, and **Revoke API Key**, which takes effect immediately with no confirmation step.

## Creating a new API key

Choose the **+** icon in the top-right corner of the table to generate a new key. Copy and store the full key immediately. It will not be shown again after the dialog closes.

## Revoking an API key

Choose the **⋮** (more options) menu on a key row and choose **Revoke**. Revoked keys cannot be reactivated. Create a new key if access needs to be restored.

<Warning>
  Treat API keys like passwords. Do not share them in plain text or commit them to version control.
</Warning>

## Related

* [Organization Settings](../organization-settings): the other configuration areas on this settings page
* [User Roles and Permissions](../user-roles-and-permissions): the roles you can assign to an API key
* [Audit Trail and Compliance](../audit-trail-and-compliance): organization-wide activity logging, including actions taken by API keys
* [Authentication](/developers/guides/authentication): how to send an API key with a request
* [Webhooks](/accountants/integrations/webhooks): the other sub-tab on Developer Access, for registering endpoints that receive record-change events