Delete an OAuth API key

Last updated: Apr 14, 2025

DEVELOPER

SUPPORT

HEALTH TECH VENDOR

OAuth API keys are used for authenticating API requests from your system to Redox. Learn about authentication methods.

You can delete duplicate or unnecessary OAuth API keys. This article contains instructions for deleting OAuth API keys in the Redox dashboard. If you'd like to create and manage via API instead, use the Delete OAuth API key endpoint.

What about deleting legacy API keys?

If you want to clean up old legacy API keys and use OAuth API keys, learn how to migrate to OAuth API keys instead. Otherwise, you can delete a legacy API key by deleting the associated source (in development or staging environments). Learn how to delete a source.

Only for engineer roles

Any user in a given environment may view connectivity settings, including sources, destinations, API keys, and authentication credentials. However, you must be assigned to an engineer role to manage them (i.e., create, verify, edit, or delete). Learn about roles.

This how-to is only for users with an engineer role.

Log in to the dashboard.
From the navigation menu, click the Developer page.
By default, the Sources tab opens and displays any configured sources and OAuth API keys. Click the Edit button of the OAuth API key you want to delete.
By default, the Settings tab displays. Scroll down to the Delete OAuth API Key section and click the Delete button.
Delete an OAuth API key
Disabled delete option
The delete option may be disabled if:
You don’t have the right role assignment. Learn about user roles.
Your organization has already migrated to production. Talk to your Technical Account Manager to delete production-level assets.

FHIR® is a registered trademark of Health Level Seven International (HL7) and is used with the permission of HL7. Use of this trademark does not constitute an endorsement of products/services by HL7®.