> For the complete documentation index, see [llms.txt](https://api.veratad.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api.veratad.com/vx/styles.md).

# Styles

The `styles` object customizes the look and feel of the VX verification experience. Use it in the Create Session request to override default UI settings.

## Colors

Defines custom color palettes. Each key (e.g., `custom-green`) maps to an array of ten hexadecimal color values representing the shades for that color.

## primaryColor

Specifies which color key from `colors` is used as the primary theme color.

## primaryShade

Selects the shade index (0–9) from the primary color palette.

## colorScheme

Sets the overall color scheme, either `"light"` or `"dark"`.

## logo\_url

URL of a logo image displayed in the interface.

## defaultRadius

Default border radius applied to components. Accepts preset values (`xs`, `sm`, `md`, `lg`, `xl`) or a custom string/number.

## button.radius

Overrides the border radius specifically for buttons. Supports the same values as `defaultRadius`.

## components.button.color

Hex value for the text color of primary filled buttons.

## assets.icons.handoff.header.main

Defines a custom icon for the handoff header:

* **alt** – alternative text for the image.
* **url** – fallback image URL.
* **srcset** – provides higher‑resolution sources for `"2x"` and `"3x"` displays.
* **width** and **height** – dimensions in pixels. Icons must fit within a 100 × 100 space, though smaller sizes are allowed.

## global.typography.font

Controls the font used across the experience:

* **family** – name of the font family.
* **normal.url** – URL to the font file. Any font type is accepted; the example uses a TTF file for demonstration.
* **normal.format** – format of the font file, such as `"truetype"`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://api.veratad.com/vx/styles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.