
Monitor an Imagild API key's expiry as an application dependency, and rotate it before work needs that credential. Keys can be created for 30 or 90 days; they are not permanent. An account can hold up to five active keys, so leave room for a replacement rather than filling every slot immediately. Review expiry in the API console.
Key Takeaways
- Track key expiry and membership expiry separately; either can interrupt access.
- Reminder dates and rotation automation belong to your application runbook, not an assumed Imagild notification service.
- Preserve task IDs during rotation so a new credential resumes owned work instead of recreating it.
Record operational metadata without recording the secret
At key creation, add a row to a private credential inventory. The row needs the key's name or non-secret prefix, owning account, application environment, expiry, responsible operator, and the secret-store entry used by the deployment.
An expiry date copied into a runbook is useful. The full Bearer value copied beside it creates a second secret-storage problem. Replicate's token-security documentation supports storing credentials in environment configuration and revoking exposed values; your own access-control policy should govern who can read the deployment secret.
The console's last-used information can help identify an apparently unused key. It is not a complete per-request audit log, and it should not be the sole evidence that a key is safe to revoke.
Build a reminder schedule around your workload
The following is an example operator policy, not a built-in Imagild email schedule:
| Checkpoint | Operator action |
|---|---|
| Seven days before expiry | Confirm the owner and plan the deployment window |
| One day before expiry | Verify that a replacement is installed and access-checked |
| After cutover | Confirm old deployments no longer depend on the old value |
| After deliberate retirement | Revoke the old key and update the inventory |
For an infrequently run application, compare expiry with its next scheduled run rather than only today's date. A key can be valid during development but expire before a monthly media job or a later download attempt.
Do the same for membership. A 90-day key does not mean the account has 90 days of API eligibility. Adding points also does not extend membership by itself.
Rotate while a slot is available
Create a replacement key under the intended account, choose its 30- or 90-day validity, and install it in the server secret store. With five active keys already present, identify and retire an unused credential through an authorized operator before trying to create another.
Make a read-only catalog request with the replacement:
curl --silent --show-error --dump-header access.headers \
--output access.json --write-out '%{http_code}\n' \
'https://imagild.com/api/relay/v1/models' \
-H "Authorization: Bearer $IMAGILD_API_KEY"
A successful access check avoids spending points merely to discover a malformed credential. If it fails, inspect the status and error code: 401 points toward key validity, while a membership-specific 403 concerns account eligibility.
Keep in-flight work independent of one deployment's key
Store the returned task ID and original operation identifier in your application's database. A valid replacement key for the same authorized account can read that account's existing task; it should not cause the application to submit a fresh generation.
If the old key expires before a result is downloaded, first restore valid authorized access. Expiry is not evidence that the generation failed or that reserved points were released. Review the failed-job decision guide before retrying work that already has a task ID.
Once downloads are available, archive approved outputs according to your own retention policy. The asset archive guide explains why a temporary service link should not be your only copy.
Verify the cutover with observable evidence
Record the access-check result, the deployment revision, and one resumed task lookup. Keep any returned error request ID, but redact Authorization headers. OWASP treats endpoint authentication and protected-resource access as continuing requirements; successful generation yesterday does not exempt today's download from them.
Imagild's key expiry and revocation controls give you a clear credential lifecycle. A monitored lifecycle is a practical reliability mechanism, rather than an uptime percentage or a promise that every unattended client will renew itself.
Related tasks
- What Should You Check Before Retrying a Failed Image or Video Job?
- How to Archive Imagild Assets Before the 90-Day Storage Window Ends
Sources and scope
- Imagild API console and integration guide: Product entry point and current API access, credential and task integration instructions; detailed facts also cross-checked against the 2026-10-28 repository contract.
- OWASP REST Security Cheat Sheet: General REST security principles: endpoint authorization, secure handling of credentials, input validation and response content-type checks. Does not define Imagild product behavior.
- Replicate API token security: General guidance for separating credentials, storing them through environment configuration and revoking exposed tokens. No Replicate platform features or guarantees are attributed to Imagild.
Product instructions were checked against the current Imagild API contract and the public model catalog. Code, budgets and acceptance checks are illustrative; this article does not claim a new paid generation test, an uptime measurement, a search-volume study or a ranking of AI citations.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Original Imagild product screenshot captured on 28 October 2026; model availability and prices may change. This image is not an API response or a performance benchmark.