Review when a Dosya API key was last used

Review when a Dosya API key was last used is easier to verify when you use one controlled item and confirm the account, workspace, and destination at each step. This guide follows the current Dosya workflow and identifies the result you should see.

Before you start

• Open Profile > Integrations > API keys in the current released client.
• Confirm the active account and workspace, then identify existing key row in API key settings.
• Use a small non-confidential test item and record its current state before changing it.
• Keep passwords, API keys, recovery keys, private links, and personal data out of screenshots and support messages.

Steps: review when a Dosya API key was last used

1. Open Profile > Integrations > API keys and confirm the active account and workspace.
2. Locate existing key row in API key settings and verify its name or identifying details.
3. Compare its name, creation time, last-used time, expiry, scope, and restrictions with the owning integration.
4. Read the displayed warning, permission, progress, or confirmation state before leaving the screen.
5. Confirm that unused or unexpected credentials are identified for rotation or revocation.
6. Refresh or reopen the relevant view once to verify the result persisted.

Expected result

The controlled workflow completes and unused or unexpected credentials are identified for rotation or revocation. The result remains visible after a refresh, reconnect, or return to the relevant screen.

Limits and important details

• Available controls depend on the current client version, account plan, workspace role, and policy.
• Processing, indexing, background transfer, or third-party authorization can delay a visible result.
• For destructive, access-changing, or automation actions, validate with disposable data before applying the workflow to important files.

Troubleshooting

The expected control is missing. Return to Profile > Integrations > API keys, confirm the active workspace, and check that your role and client version support the action.

The operation is rejected or stalls. Read the exact message and check permissions, locks, storage, network state, source availability, and any third-party authorization before retrying.

The result is still unclear. Repeat with one small test item, then contact support with the time, client version, workspace, and a nonsecret error or request identifier.

Related guides

• Create an API key
• Choose key scopes