Reference

Errors and limits

How errors look, what each status code means, and how much you can send.

Error format

Errors are JSON: { error: { code, message, fields? } }. Invalid listings list every problem field by field. /oauth/token answers in the OAuth format, { error, error_description }.

json

422 Unprocessable Entity
{ "error": { "code": "invalid_listing", "message": "The request has problems.",
  "fields": [ { "field": "modifiedAt", "message": "Use ISO 8601 with a time zone, e.g. 2026-11-10T09:30:00+10:00. A time zone (Z or +10:00) is required." },
              { "field": "colour", "message": "Unknown field. A listing has: type, status, modifiedAt, …" } ] } }

Status codes

202: Accepted: stored and queued. Read the report, or wait for the webhook.
400: A malformed request (empty body, bad listing ID).
401: Missing, expired or revoked access token.
403: Not allowed: agency not connected, sandbox ID mismatch, test key for a live action, or a suspended account.
404: No such delivery or listing.
413: Over 20 MB.
422: Field errors in the listing.
429: Rate limited. Wait for Retry-After seconds.

Limits

API: 300 requests a minute per account and environment, and the same for access tokens per key.
Deliveries: 600 per agency per hour, across all channels, including API deliveries for a single agency.
File size: 20 MB per file or request. Zips may unpack to at most 25 MB per file, 80 MB in total and 3,000 files.
New listings: 2,000 per agency per day. Agencies awaiting review: 50 per day, and their pages aren't offered to search engines until approved.
Photos: Up to 36 per listing; the first 30 are copied and resized, any more stay as your own links.
Connections: Up to 100 new requests a day.