Mint Key

Create another key on your account.

The value is in this response and nowhere else. Keys are stored as hashes, so a key that is not written down is a key that has to be replaced rather than recovered.

Every key on an account shares that account's credits, job history and job ceilings, and carries its own request rate limit. Several is the ordinary arrangement: one per service or per environment, so that revoking one does not stop the others.

This is also how you rotate without downtime — create the new key, move your clients onto it, then revoke the old one. There is no window in which nothing works, which is why there is no single "rotate" call.

An account is given a limited number of new keys in any hour, whichever of its keys asks; past it this is refused with 429 and Retry-After. Revoking is never limited. Each request also counts against the calling key's own request rate, as a submission does.