# Reference Data

Read-only catalogs (equipment, charge codes, special requirements)
referenced by id from other resources.

Every catalog also answers on its short top-level path, so
`GET /v1/charge-codes` and `GET /v1/reference-data/charge-codes` are
the same endpoint. The documented `/reference-data/*` form is canonical
— it keeps the catalogs grouped here as more are added (port codes,
cities, zip codes) — and the short form is a convenience alias.


## List equipment

 - [GET /reference-data/equipment](https://docs.mvmnt.io/apis/openapi/reference-data/listreferenceequipment.md): Read-only catalog of equipment types. The ids are what order and load
equipment arrays reference. The list is system-managed and small —
fetch it once and cache it, or hardcode the ids your integration uses.

The catalog is global and organization-independent: every
authenticated organization sees the same rows.

## List charge codes

 - [GET /reference-data/charge-codes](https://docs.mvmnt.io/apis/openapi/reference-data/listreferencechargecodes.md): Read-only catalog of charge codes. The integer ids are what charge
chargeCodeId fields reference. The list is system-managed — fetch it
once and cache it.

The catalog is global and organization-independent: every
authenticated organization sees the same rows.

## List special requirements

 - [GET /reference-data/special-requirements](https://docs.mvmnt.io/apis/openapi/reference-data/listreferencespecialrequirements.md): Read-only catalog of special requirements (equipment accessories,
driver services, freight handling, location constraints). The ids are
what order and load specialRequirements arrays reference. Filter by
type to get one category.

The catalog is global and organization-independent: every
authenticated organization sees the same rows.