# List special requirements

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.

Endpoint: GET /reference-data/special-requirements
Version: 1.0.0
Security: BearerAuth

## Query parameters:

  - `type` (string)
    Only return requirements of this type
    Enum: "EQUIPMENT", "DRIVER", "FREIGHT", "SHIPPER_LOCATION"

## Response 200 fields (application/json):

  - `data` (array, required)

  - `data.id` (string, required)
    Special-requirement id (referenced by order/load specialRequirements arrays)

  - `data.name` (string, required)
    Display name (e.g., "Tarps")
    Example: "Tarps"

  - `data.type` (string, required)
    What the requirement applies to.
- EQUIPMENT: Equipment accessories (e.g., tarps, straps)
- DRIVER: Driver services (e.g., team service, TWIC)
- FREIGHT: Freight handling characteristics
- SHIPPER_LOCATION: Location constraints
    Enum: "EQUIPMENT", "DRIVER", "FREIGHT", "SHIPPER_LOCATION"

## Response 400 fields (application/json):

  - `error` (string, required)
    Error code

  - `message` (string, required)
    Human-readable error message

## Response 401 fields (application/json):

  - `error` (string, required)
    Error code

  - `message` (string, required)
    Human-readable error message

## Response 429 fields (application/json):

  - `error` (string, required)
    Error code

  - `message` (string, required)
    Human-readable error message