
Pause an Imagild API key when you deliberately need a temporary stop and still trust the credential. Revoke it when the credential is exposed or permanently retired. A paused key can be resumed while otherwise eligible; a revoked key cannot be restored. Neither action cancels a generation that was already accepted or automatically refunds its points.
Make the decision in the Imagild API console, using the owning account and the key's name or masked prefix. Keep the complete secret out of screenshots, tickets and browser code.
Key Takeaways
- Pause is reversible; revocation is a permanent credential retirement.
- A paused key cannot authenticate its normal API reads or writes until resumed, even if its task already exists.
- Expiry, membership and task billing remain separate checks after a key is resumed.
Choose from the situation, not the error message alone
| Situation | Appropriate next step | Important boundary |
|---|---|---|
| Planned maintenance and the secret remains trusted | Pause the intended key | Existing accepted tasks still need reconciliation |
| A secret appeared in a public repository or shared log | Revoke and replace through your secure process | Hiding the visible copy does not invalidate copies |
| A retired application no longer needs access | Revoke its credential after checking dependencies | Do not retire an unrelated active integration |
| The console shows Expired | Plan an authorized replacement | Resume does not extend the expiry date |
| Membership no longer permits API use | Resolve the account's access condition | An otherwise active key is not membership itself |
For exposure, follow the credential incident guide. A temporary pause can leave you with a credential you should never trust again if someone else copied it. This guide does not suggest resuming an exposed value.
Pause and resume the intended key
Open the console and identify the correct account, environment, key name and prefix. Use the name-or-prefix search and status filter if several keys are present. If the key is older than the currently loaded history, load older keys before concluding that it is missing.
For a trusted, unexpired key, select Pause in its row. Wait for the operation to finish and confirm that the row shows Paused. Record the change in your own operational notes if an application depends on it.
When the planned stop ends, select Resume and confirm the row's current status. Expiry and membership still apply; a resume action does not renew either one. The expiry-monitoring guide explains replacement planning separately.
A fictional example: a team pauses the key for its staging application during a maintenance window. Before resuming, it checks that the deployment still reads the intended secret-store entry and that no leak was reported. It does not create a production image just to prove that the pause button changed state.
Revoke deliberately and preserve task references
When revocation is appropriate, identify the intended row, choose Revoke, then review the explicit Confirm revoke action. Confirm only after checking which deployment uses that key. The console also offers a cancellation action before the confirmation is submitted.
After revocation, verify the row is marked Revoked and remove the retired credential from the application's active configuration. If the application must continue, an authorized operator should install a replacement securely. The masked value in history cannot reconstruct a lost full secret.
Keep the original task IDs and request records during this change. Revoking the key does not delete generated media; the revocation-versus-data guide covers that separate question.
Understand what happens to already accepted work
Key management controls subsequent authentication and admission. It does not withdraw a task that the service already accepted. That task can still progress, produce a result or require reconciliation under its original quote.
Pausing also blocks authenticated status and download calls made with that paused key. A failed read therefore does not establish that the generation failed. Use the account's supported history views to investigate, or restore appropriate authorized access when safe. Do not resubmit the generation with a new key merely because the old key now returns an access error.
The membership-and-points guide explains why restoring a credential alone may not resolve an account-level access problem.
Verify the change without another paid task
Check the visible key state and the application's configured credential reference. Where an access check is needed, use a documented read-only operation rather than a generation request. Retain the exact returned error and time, distinguishing credential access from the last known task status. Never put the Bearer value into the diagnostic record.
Sources and scope
This company guide describes the current API console and documented key-management behavior checked October 30, 2026. It is an operational explanation, not a claim that every lifecycle action was exercised on a production credential. No live key was created, paused, resumed or revoked while preparing it.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. Report a correction.
Cover: AI-generated conceptual illustration; not an application screenshot, observed result, private account record or privacy guarantee.