## Retrieve Available Fonts

Get a list of available fonts that can be used for branding your payment interface. This endpoint returns a comprehensive list of fonts that are supported for customizing the typography of your payment forms.

The response includes:
- Font family names (e.g., 'Noto Sans', 'Roboto')
- Font categories (sans-serif, serif, monospace, display, handwriting)
- Available font weight variants for each font family

Common use cases for this endpoint include:
- Populating font selection dropdowns in your branding interface
- Validating font choices before updating branding settings
- Displaying available font options to users
- Building font preview functionality

This endpoint requires authentication and returns the same font list for all merchants, as fonts are globally available across the platform.

**Note:** Font variants are filtered to exclude italic styles and are converted to readable weight names (e.g., 'Bold', 'Medium', 'Light').

## Endpoint signature

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

{}
```

Returns: array

## Response attributes

### `family` (string)

**Always present**. The font family name (e.g., 'Noto Sans', 'Roboto').

### `category` (string)

**Always present**. The font category that describes the font style and usage.

Possible values:

- `sans-serif`
- `serif`
- `monospace`
- `display`
- `handwriting`

### `variants` (array)

**Always present**. Available font weight variants for this font family.

Possible values:

- `Thin`
- `ExtraLight`
- `Light`
- `Regular`
- `Medium`
- `SemiBold`
- `Bold`
- `ExtraBold`
- `Black`

## 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.