RENTZOOBI FOR LISTING PARTNERS

A feed your team can work with.

The RentZoobi XML v1 specification, examples and delivery workflow in one place. Use the schema and field dictionary together when building your exporter.

Start with the specification

All sample listings are synthetic. The schema describes the structure; the field dictionary and server validation also enforce accepted values and business rules.

Deliver a feed

  1. Create an organization and confirm access

    An organization owner opens Partner feeds. The workspace reports whether delivery is enabled in the current environment. Confirm your identity when creating or rotating credentials.

  2. Save the connection credential securely

    The credential is shown once. Store it in your server’s secret manager. Use one connection per source and organization; never put the credential in a URL, client-side code, XML file or support request.

  3. Validate before importing

    Send a dry run first, or upload XML from the owner workspace. Check the response and correct each invalid row before sending a reviewable delivery.

POST /api/v1/partner-feeds/{feed_id}/deliveries?dry_run=true
Content-Type: application/xml
X-Partner-Token: <your connection credential>
Idempotency-Key: <a new UUID for this delivery>

<the contents of your XML file>

Send the request to your approved RentZoobi environment over HTTPS. The integration guide includes the complete request and retry instructions. A dry run does not create or update listing drafts.

Collect a hosted feed

A partner can host its RentZoobi XML file at an approved HTTPS address. Support binds that source and its server credential to your organization’s feed connection. An owner then selects the approved source, confirms identity and chooses manual collection or a scheduled refresh in the feed workspace.

The workspace shows the last attempt, result and received delivery. Scheduled collection requires an active worker in the environment; saving an interval alone does not start a worker. Collect now stages new content for review. Pause stops scheduled collection while retaining existing listings and receipts.

Sources must serve the documented XML directly. Redirects, private-network addresses and compressed files are rejected. Credentials stay in the server’s secret manager and never belong in the URL or a support email. Unchanged files do not create duplicate receipts; an empty file response does not remove listings.

Connect authorized Rentari listings

Rentari’s dedicated exporter uses the RentZoobi XML format and stable listing references. Only the source’s permitted inventory with RentZoobi distribution enabled and the required syndication consent is eligible. Private renter, lease, payment and screening records are excluded.

Arrange the Rentari source and RentZoobi connection through partner support, validate a synthetic feed, then review the first authorized delivery. Deployment and source activation are separate from having the exporter code. Photos and publication checks still use the RentZoobi listing workflow.

Review before applying

A regular delivery creates a reviewable receipt. An authorized owner inspects the proposed actions, invalid rows and conflicts, then explicitly applies ready rows. Applying upserts prepares listing drafts or changes for review; it does not publish them.

Review explicit withdrawals carefully: applying a withdrawal can remove its linked listing from public discovery. Rows with validation errors or conflicts need correction. A successful HTTP response alone does not mean every listing was applied.

Open feed workspace

Keep updates predictable

Stable identifiers
Keep each listing’s external ID unchanged across updates. Reusing an ID for a different space can update the wrong record.
Explicit changes
Send deliberate upserts and withdrawals. Omitting a listing from a file is not a request to delete it.
Safe retries
Retry the same delivery with the same idempotency key and unchanged content. A corrected file needs a new key; a corrected regular delivery also needs a sequence higher than the connection’s last received sequence. Regular deliveries reserve their sequence even when rows are invalid. Follow any Retry-After response.
Conflicts need review
If a linked listing changed after preview, refresh the source data and submit a new delivery. Do not overwrite a newer edit blindly.
Listing data only
Send data you are authorized to distribute. Keep tenant data, applications, identity documents, screening reports, payment details and secrets out of feeds.

Know the supported format

This integration accepts the documented RentZoobi XML v1 format. Existing Zillow, MITS, Yardi or other vendor exports may need a mapping or adapter. A vendor name does not imply a tested integration or a partnership.

Hosted collection is limited to approved sources using this format. FTP delivery, vendor-specific certification and automatic outbound syndication are not offered by this workflow. Share your format and requirements through a partnership inquiry.