Errors
Standard problem responses, request IDs and safe retry rules.
On this page
Errors use HTTP status codes and application/problem+json (RFC 9457):
The same correlation ID appears in X-Request-Id. Keep it when contacting support. Errors never echo API keys, request bodies, SQL text or storage credentials. Branch on HTTP status rather than matching the message.
Status codes
Validation errors
A 422 can include errors, each containing type, loc and msg. For example, loc: ["body", "pricing", "sale"] identifies the invalid field. Input values are deliberately omitted.
Retry rules
GET requests are safe to retry. Property and contact creation support idempotency keys: reuse the same key and body after a lost response. Without a key, check whether creation succeeded before retrying. Repeating the same publication request is safe. Do not poll failed jobs indefinitely; correct the cause first.
Existing rental ingestion ignores known phone numbers; inquiry creation can return a conflict when a previous attempt was stored. Server-side outreach errors do not expose internals.