Rotate a swap API key without losing in-flight swaps

Rotating an API key should change how your server authenticates to a provider. It should not erase pending swaps or generate new wallet signatures automatically.

Separate credential version from trade identity

Assign each request a safe credential-version label for operational tracing. Keep the secret itself outside logs. A swap attempt retains its own ID, chain, account, quote reference and transaction or order hash regardless of which credential authenticated a later status query.

OWASP describes secret rotation as a lifecycle process. Apply it through a controlled configuration change: provision the replacement credential, verify its permitted endpoints, move new traffic, observe authentication errors and retire the old credential according to the incident or maintenance plan.

Handle provider-specific bindings

Some services can bind quotes, fees or account access to a particular project. Do not assume a payload created under one credential is reusable under another. If the provider requires a fresh quote, obtain one and ask for a new review when its terms change.

For a transaction already broadcast, continue chain-based receipt tracking even if the quote API is unavailable. For an off-chain order, preserve its order hash and use the provider's documented status mechanism. Key rotation is not order cancellation.

Exercise the operational path

Test rotation while a quote is pending, while an approval is confirming and after a transaction hash is stored. The application should recover to a valid next state in each case. It must not interpret an authentication failure as proof that the underlying swap failed.

If a credential was exposed, revoke or replace it promptly through the authorized account workflow and inspect usage. Changing a provider key does not remedy exposure of a wallet private key; those credentials control different systems.