> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.hopnow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Object IDs

> Resource id format, prefixes, and common object fields

Every resource is addressed by an `id` — a short resource prefix followed by 24 random lowercase alphanumeric characters (`a–z`, `0–9`), e.g. `cus_x7k2m9p4q1w8e5r3t6y0u2i4`. Ids are stable and unique. Treat them as opaque strings: store them as-is and do not parse anything beyond the prefix.

| Prefix  | Resource                     |
| ------- | ---------------------------- |
| `cus_`  | Customer (Platform customer) |
| `acct_` | Account (end customer)       |
| `aap_`  | Associated person (KYB)      |
| `doc_`  | Document (KYB / identity)    |
| `bene_` | Beneficiary                  |
| `dest_` | Payment destination          |
| `va_`   | Virtual account              |
| `api_`  | Deposit                      |
| `apo_`  | Payment                      |
| `atx_`  | Transfer                     |
| `wh_`   | Webhook endpoint             |

## Common object fields

Most single-object responses include these fields in addition to the resource-specific attributes:

<ResponseField name="object" type="string">
  Object type discriminator, e.g. `"account"`.
</ResponseField>

<ResponseField name="created" type="datetime">
  Creation timestamp (ISO 8601, UTC).
</ResponseField>

<ResponseField name="updated" type="datetime | null">
  Last update timestamp.
</ResponseField>

<ResponseField name="created_by" type="string | null">
  Actor that created the record.
</ResponseField>

<ResponseField name="updated_by" type="string | null">
  Actor that last updated the record.
</ResponseField>