Skip to main content
The API keys endpoints manage sub-keys: additional keys you can mint under the account and revoke individually. A sub-key is not the same thing as your main account key, which lives in the dashboard under Profile, section API key, and is not managed through these endpoints. All requests go to https://api.nodemaven.com/api/v2/base/ and carry the header Authorization: x-api-key YOUR_API_KEY. See the NodeMaven API overview for the shared basics.

Endpoints

Minting a sub-key

ApiKeyCreateRequest has two fields:
expires_at is optional, and because it is nullable you can set it explicitly to null to say the sub-key should not expire. Leaving it out has the same practical effect.

Revoking

Both revoke operations are soft deletes, so the record is marked revoked rather than erased.
POST /api-keys/revoke-all revokes every sub-key on the account in one call. Any integration authenticating with a sub-key stops working immediately. There is no per-key exemption and no undo exposed by this endpoint. Use DELETE /api-keys/{id} when you only mean to retire one.
A successful single revoke returns 204, so no body comes back.

Why a mint fails

POST /api-keys has two failure codes, and they mean different things: In both cases the sub-key was not created.