# Create an equipment posting

**Idempotency-Key** *(optional header)*: Supply a client-generated UUID v4 to enable safe retries. On a cache hit the server replays the original 201 response without writing a duplicate posting. The key is scoped to your account and expires after 24 hours.

Endpoint: POST /v2/postings/equipment
Version: v2
Security: OrgTokenBearer

## Header parameters:

  - `Idempotency-Key` (string)
    Client-generated UUID v4 for safe retries. Re-sending the same key within 24h replays the original 201 without creating a duplicate posting.

## Request fields (application/json):

  - `dateAvail` (string, required)
    Equipment available date/time in ISO 8601 UTC format (e.g. 2026-07-01T00:00:00Z). Non-UTC values are coerced to UTC.
    Example: 2026-07-20T08:00:00Z

  - `srceCity` (string, required)
    Source city name. Must match a known city (see city lookup) together with SrceSt.
    Example: Sarnia

  - `srceSt` (string, required)
    Source state/province code (2 letters, e.g. "ON", "TX").
    Example: ON

  - `srceRadius` (integer)
    Search radius in miles around the source city (50–500).
    Example: 200

  - `destCity` (string, required)
    Destination city name. Must match a known city (see city lookup) together with DestSt.
    Example: Brampton

  - `destSt` (string, required)
    Destination state/province code (2 letters, e.g. "ON", "TX").
    Example: ON

  - `destRadius` (integer)
    Search radius in miles around the destination city (50–500).
    Example: 200

  - `vehicleSize` (string, required)
    Single-letter vehicle size code — see GET /v2/reference/vehicle-sizes (e.g. "T" for TL).
    Example: T

  - `vehicleType` (string, required)
    One or more single-letter vehicle type codes concatenated together — see GET /v2/reference/vehicle-types (e.g. "VR" for Van + Reefer).
    Example: VR

  - `contactEmail` (string)
    Contact email for this posting. Optional — defaults to your account's own email when omitted. Does not have to match the authenticated account if supplied.
    Example: dispatch@example.com

  - `contactPhone` (string)
    Contact phone for this posting. Optional — defaults to your account's own phone when omitted.
    Example: null

  - `comment` (string)
    Free-text comment shown alongside the posting (max 180 characters).
    Example: Reefer unit available

  - `postingAttrib` (string)
    One or more single-letter vehicle attribute codes concatenated together — see GET /v2/reference/vehicle-attributes (e.g. "AZ" for Air Ride + Hazmat).
    Example: AZ

  - `corridor` (string)
    "C" (corridor) to widen the match beyond the source/destination radius circles to include postings reasonably along the route, or "R" (radius) for standard radius-only matching. Automatically overridden to "R" when source and destination are the same city.
    Example: C

  - `length` (integer)
    Equipment length.
    Example: 53

  - `weight` (integer)
    Equipment weight capacity.
    Example: 45000

  - `rate` (number)
    Rate amount. Brokers: total trip cost. Carriers: per-mile rate.
    Example: 2.1

  - `currency` (integer)
    Currency code: 0 = USD, 1 = CAD.
    Enum: 0, 1

## Response 201 fields (application/json):

  - `token` (integer)
    Unique identifier for the newly created posting. Use this same value as the {token} in GET /v2/leads/equipment/{token} to retrieve leads for this posting, and in GET/DELETE /v2/postings/equipment/{token} to look up or remove it.

  - `message` (string)
    Human-readable confirmation message.

  - `createdAt` (string)
    Date/time the posting was created, in UTC.

## Response 400 fields (application/json):

  - `type` (string)

  - `title` (string)

  - `status` (integer)

  - `instance` (string)

  - `traceId` (string)

  - `detail` (string)
    the details of the error

  - `errors` (array)

  - `errors.name` (string)
    the name of the error or property of the dto that caused the error

  - `errors.reason` (string)
    the reason for the error

  - `errors.code` (string)
    the code of the error

  - `errors.severity` (string)
    the severity of the error

