API Keys
Create and manage project-scoped API keys
API Keys
API keys provide programmatic access to the Fugoku API. They are scoped to a project and can be revoked at any time.
List API Keys
GET /v1/api-keysReturns all API keys for the current project.
Response:
{
"data": [
{
"id": "key-abc123",
"type": "api-keys",
"attributes": {
"name": "Production CI",
"prefix": "<generated-prefix>",
"expiresAt": "2027-01-01T00:00:00Z",
"revoked": false,
"createdAt": "2026-01-01T00:00:00Z",
"lastUsedAt": "2026-07-31T12:00:00Z"
}
}
]
}Note: The full API key is only shown once at creation time. The
prefixfield shows the first 12 characters for identification.
Create API Key
POST /v1/api-keysRequest Body:
{
"name": "My API Key",
"expiresAt": "2027-01-01T00:00:00Z"
}Returns the full key value once. Store it securely.
Response:
{
"data": {
"id": "key-abc123",
"type": "api-keys",
"attributes": {
"name": "My API Key",
"key": "<generated-api-key>",
"prefix": "<generated-prefix>",
"expiresAt": "2027-01-01T00:00:00Z",
"createdAt": "2026-01-01T00:00:00Z"
}
}
}Revoke API Key
DELETE /v1/api-keys/:idRevokes an API key immediately. Returns 204 No Content.
Provider API Keys (IAM)
Provider API keys (for cloud provider credentials) are managed under the IAM endpoints:
GET /v1/iam/api-keys
POST /v1/iam/api-keys
POST /v1/iam/api-keys/:keyId/rotate
DELETE /v1/iam/api-keys/:keyIdSecurity
- API keys are hashed using bcrypt before storage
- Only the key prefix (first 12 chars) is stored in plaintext for lookup
- Key prefixes:
fk_live_for production,fk_test_for test - Keys can be scoped to an expiration date
- Revoked keys are permanently invalidated