---
title: "Set the maximum key lifetime"
method: PUT
path: "/v1/authz/settings"
tags: ["Access"]
---

# Set the maximum key lifetime

`PUT /v1/authz/settings`

## Request

- Base URL: `https://api.openrelay.inc`
- URL: `https://api.openrelay.inc/v1/authz/settings`
- Auth: HTTP bearer

Sets maxKeyLifetimeDays, from 0 to 3650, and returns the saved settings. New API keys must expire within that many days; 0 lets keys never expire.
Requires a signed-in session.

Requires the `guardrail.manage` permission. See [Permissions](https://docs.openrelay.inc/docs/permissions) for the roles and API key permissions that include it.

## Request body

- AuthzSettings
  - `maxKeyLifetimeDays` integer, required: New keys must expire within this many days; 0 means keys may never expire.
  - `updatedAt` string
  - `updatedBy` string

## Response `200`

Updated

- AuthzSettings
  - `maxKeyLifetimeDays` integer, required: New keys must expire within this many days; 0 means keys may never expire.
  - `updatedAt` string
  - `updatedBy` string

## Other responses

- `400`: The request is invalid
- `401`: Missing or invalid API key
- `403`: The caller is authenticated but may not do this. The caller's role or the API key's permissions do not allow it, or the request targets another organization (FORBIDDEN, or NOT_A_MEMBER for a session); a permission denial also names the action it needed (permission), which kind of policy denied it (deniedBy) and the deciding policy ids (policies). Or the organization is suspended pending review (ORG_SUSPENDED) or has been deleted (ORG_DISABLED). A new API key or a wider scope clears neither of the last two; see [Account and balance refusals](https://docs.openrelay.inc/docs/errors#account-and-balance-refusals). A user session whose email address is not confirmed is refused on every operation (EMAIL_UNVERIFIED); confirm the address from the confirmation email, then sign in again.
- `404`: Resource not found

## Changes

- **2026-10-26** `7fe59d94a9f5`: 4 info
  - added the optional property `requestId` to the response with the `400` status
  - added the optional property `requestId` to the response with the `401` status
  - added the optional property `requestId` to the response with the `403` status
  - added the optional property `requestId` to the response with the `404` status
- **2026-10-10** `12b2fcbcc298`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/openrelay/apis/openrelay-api/changes/v1/authz/settings/put.md)

---

[API](https://skmtc.dev/openrelay/apis/openrelay-api.md) - [All operations](https://skmtc.dev/openrelay/apis/openrelay-api/llms.txt) - [OpenAPI document](https://skmtc.dev/openrelay/apis/openrelay-api/revisions/7fe59d94a9f5?raw)