Sending listings

HTTPS push

For systems that send files over HTTPS. The agency creates a push token on its Connections page and gives it to you.

Send a file

Send the token as a Bearer token. The body is a REAXML document (application/xml), a zip (application/zip), or a multipart file field.

http

POST https://liststream.com.au/api/feeds/push
Authorization: Bearer lsf_...
Content-Type: application/xml

<propertyList>...</propertyList>

202 Accepted
{ "id": "6f86c062-...", "status": "queued",
  "report": "https://liststream.com.au/api/feeds/deliveries/6f86c062-..." }

GET https://liststream.com.au/api/feeds/deliveries/6f86c062-...
Authorization: Bearer lsf_...

{ "status": "done",
  "counts": { "new": 1, "updated": 0, "unchanged": 0, "skipped": 0 },
  "items": [ { "uniqueId": "EX-1", "agentId": "EXAMPL", "result": "new", "listingId": "..." } ],
  "errors": [] }

The report

Every listing in the delivery is listed with its result: new, updated, unchanged, removed or skipped, and a message when it was skipped.

Tokens

A wrong, turned-off or replaced token gets 401. Issuing a new token in the dashboard stops the old one.