Objects

Eight listable resources — tickets, properties, units, assets, vendors, inspections, turns and meters — plus occupancy ingest. Every list uses the same envelope and the same cursor.

The list envelope

{
        "data": [ { /* one ticket object */ }, { /* … */ } ],
        "next_cursor": "v1:48213",
        "limit": 2
      }

Filters

Every filter is optional and is sent as a query parameter, alongside limit and cursor.

GET /tickets

GET /assets

GET /units

GET /inspections

GET /turns

GET /meters

/properties and /vendors take limit and cursor only. A meter's readings take limit and cursor on GET /meters/{meter_id}/readings — the meter is in the path. Status values are Title-Case. An unknown ?status= is 422 — “A filter value is outside its enum.” — not an empty page. The document lists that 422 on tickets, properties, units, assets, vendors, inspections and turns.

Paging

Keyset cursors, not offsets: a page is “the next limit records after this id,” so inserts while you page do not shift or duplicate rows. Follow next_cursor until it is null. There is no total count.

Filters compose with cursor: a next_cursor issued under one filter set is replayed under the same set. Do not change filters mid-walk.

curl "https://app.fixgrid.app/api/v1/tickets?limit=200&cursor=v1:48213" \
        -H "Authorization: Bearer $FIXGRID_KEY"

A malformed cursor is a 400. A limit above 200 is silently clamped to 200 — the applied value comes back as limit in the response, so read it rather than assuming yours was honoured. A limit that is not a positive integer is a 400 — see Errors.

Fetch one

Shared keys

ticket

Field names follow MITS conventions where MITS has an opinion. The full table for every object is generated into the reference; this is the shape.

Writing a ticket

Scope write. Both verbs require the Idempotency-Key header (64 characters or fewer). Full request bodies are generated into the reference.

Creates a ticket on the given unit, status always Open. Required body: unit_id, title, category. Sending status is 422 invalid_request — the document: “This endpoint always creates a ticket with status 'Open'. Remove `status` from the request body.” A key with no minting administrator is 422 created_by_missing. Replay and mismatch are 409.

Changes a ticket's status. There is no transition graph — any status is reachable from any other, including reopening Completed or Cancelled. note is required (5+ words) only when status is Completed; cancellation_reason_code only when Cancelled, and only one of the seven codes in the table above — any other value is 422 invalid_request: “The `cancellation_reason_code` field must be one of: resident_cancelled, duplicate_ticket, resolved_independently, wrong_property, no_access_repeated, scheduled_for_later, see_notes.” Any extra key is one 422. cancellation_notes without see_notes is 400. A company that requires a close-out photo refuses Completed as 422. Replay and mismatch are 409. Sentences are on the reference row.

vendor

The full table is generated into the reference; this is the shape that is unique to vendor.

inspection

Ops inspections only. Consulting-engagement walks (DD / PCA / DD Unit Walk) are excluded. A standalone Unit Acceptance walk with no engagement stays in. Fetching an id this key cannot see is 404 not_found — “No inspection with that id is visible to this key.” Full table in the reference.

turn

A turn is the transition record — an occupancy record: move-out, move-in, projected ready date — not the unit. Every transition lists, including a plain first-ever move-in with no move_out_date; the unit's own status rides GET /units. It is the same object the turn.status_changed and turn.schedule_changed webhooks carry (see the events). Fetching an id this key cannot see is 404 not_found — “No turn with that id is visible to this key.” Full table in the reference.

meter

Utility meters across electric, gas, water, sewer, trash and other, including inactive ones. Fetching an id this key cannot see is 404 not_found — “No meter with that id is visible to this key.” Readings are a third paginated route, oldest first. Full tables in the reference.

occupancy

Ingest only — there is no occupancy list or fetch. Scope write. Both verbs require Idempotency-Key and a provider slug: required, lower-cased, 40 characters max. The response is an OccupancyRecord. Full bodies in the reference.

Records a notice to vacate on the unit's current resident. Required: move_out_date, provider. external_id is capped at 120 characters; over the cap is 400 invalid_request before anything is written — see field caps.

Creates a new resident tenancy on the unit. Required: move_in_date, lease_start_date, parties, provider. The document on ordering: “Parties are stored with named leaseholders first (a stable reorder); guarantors and any other entries follow in their original relative order. The response echoes the STORED order, which may differ from the request order.” Every party field has a cap — first_name 80 · last_name 80 · email 150 · phone 20 · external_id 120 — and so does the top-level external_id (120). Over a cap is 400 invalid_request before anything is written — see field caps.