Pagination and filtering

List endpoints such as GET /cars and GET /customers share the same query parameters and response shape.

Query parameters

Parameter	Default	Description
`page`	`1`	1-based page number.
`limit`	`50`	Records per page, from `1` to `200`.
`updatedAfter`	—	ISO 8601 timestamp with a timezone offset. Returns only records updated at or after this time.
`ids`	—	Comma-separated list of IDs (up to 200) to fetch specific records.

Some endpoints add their own filters (for example, customerId or status). They are listed on each endpoint’s page.

Response shape

{
  "data": [
    { "id": "4f7c2e0a-…", "year": 1967, "make": "Ford", "model": "Mustang" }
  ],
  "page": 1,
  "limit": 50,
  "total": 132
}

Most list endpoints return the most recently updated records first. Keep requesting the next page until page * limit >= total. Single-record endpoints (GET /cars/{id}, POST, PATCH) wrap the record in data:

{ "data": { "id": "4f7c2e0a-…", "year": 1967, "make": "Ford", "model": "Mustang" } }

Keep another system in sync

To mirror records into another system without re-downloading everything:

Do one full sync

Page through the list endpoint with limit=200 and store every record. Record the time you started the sync.

Pull only changes

On each later run, pass updatedAfter set to the start time of the previous run. Records that changed while the previous run was in progress are included again rather than missed.

curl "https://www.carstoragesoftware.com/api/v1/cars?limit=200&updatedAfter=2026-10-01T00:00:00Z" \
  -H "Authorization: Bearer $CSS_API_KEY"

Get started

Cars

Customers

Contacts

Locations

Parking

Event types

Appointments

Communications

Marketing

Query parameters

Response shape

Keep another system in sync

​Query parameters

​Response shape

​Keep another system in sync

Query parameters

Response shape

Keep another system in sync