## Update an API key

Update the name of an existing API key for your merchant account. This allows you to change the descriptive
name that helps identify the key's purpose.

The key's actual value and functionality remain unchanged - only the display name is modified.

## Endpoint signature

```http
POST https://api.reservepay.com/merchants/update-key HTTP/1.1
Content-Type: application/json
Accept: application/json
Authorization: Bearer <token>

{
  key_id: string,
  name: string,
}
```

Returns: boolean

## Request arguments

### `key_id` (string)

**Required**. The unique identifier of the API key you want to update. This ID was provided when the key was first generated.

### `name` (string)

**Required**. The new descriptive name for the key. Choose a name that clearly identifies the key's purpose and usage context.

## Errors specific to this endpoint

### `NOT_FOUND`

This error occurs when no active API key with the provided ID exists in your merchant account.

## Errors common to all endpoints

### `UNHANDLED_ERROR`

This error occurs when the server encounters an unexpected internal error that
it cannot handle gracefully. This typically happens due to bugs, infrastructure
issues, or edge cases that weren't anticipated during development.

### `INVALID_ARGUMENTS`

This error occurs when the request contains invalid or missing parameters.
Common cases include missing required fields, or values that don't match the
expected format or type.

### `BAD_VERSION`

This error occurs when making requests to an API version that does not exist.
This commonly happens when using an outdated SDK or when the API version
specified in the request URL is incorrect.