# Connect a Rentari listing feed Use a dedicated Rentari export source and one RentZoobi organization-scoped feed connection. The exporter and collector must be deployed and enabled in the intended environment before real inventory can flow. Source approval, delivery, application and publication are separate outcomes. ## Prepare the partnership 1. Contact **info@rentari.ai** with the source organization, authorized contact, intended RentZoobi organization, approximate inventory count, markets and desired refresh interval. Do not email a credential, renter record or private document. 2. Identify the Rentari owner and permitted listings. In the listing’s **Listing sites** controls, enable **RentZoobi** only for listings authorized for that destination and retain the required syndication consent. A shared company login or subscription does not grant cross-product access. 3. Have the operator provision a dedicated Rentari source and approve its exact HTTPS export URL for one RentZoobi organization and feed. Keep the source credential in the existing server secret manager. The owner workspace selects an approved source; it does not accept arbitrary URLs or secret values. 4. Test with [synthetic Rentari XML](sample-rentari.xml), its [withdrawal example](sample-rentari-withdraw.xml), the [schema](rentzoobi-feed-v1.xsd) and [field dictionary](field-dictionary.md). Both Rentari examples are generated by the dedicated exporter using synthetic inputs. Follow the existing [integration guide](integration-guide.md) for validation and receipts. ## Export endpoint ```text GET {RENTARI_ORIGIN}/api/v1/marketing/feed/rentzoobi/{source_id}.xml X-Feed-Token: ``` `RENTARI_ORIGIN` is the approved HTTPS origin for the deployed environment; `{source_id}` is the operator-issued source identifier. This path is an API contract, not confirmation that an environment or source is active. Do not place the credential in the URL or XML. The source is bound to its Rentari owner and may be narrowed to an explicit listing allowlist. - Only eligible, explicitly opted-in listings with current consent are exported. Source approval never permits exporting an unrelated owner’s inventory. - Public listing facts are mapped into RentZoobi XML v1. The export does not include renter contacts, applications, leases, payments, screening reports or account secrets. - External IDs and property keys are stable. Do not recreate the source or change its identifiers to work around a conflict; doing so can produce duplicate inventory. - Sequence increases when the exported snapshot changes. Repeated collection of unchanged content preserves its sequence and bytes. - Listings previously exported but no longer eligible produce explicit withdrawal records. Repeated withdrawals are retained so a missed collection does not leave a removal instruction behind. - A source that has never exported any eligible listing may return HTTP 204. It is not a withdrawal instruction. Disabling the source credential stops access; it does not itself withdraw listings. - One source supports at most 100 known listing identities, including retained withdrawals, and a 512 KiB file. Oversized snapshots fail without silently truncating records. Coordinate source partitioning with support before onboarding a larger portfolio. ## Set up collection in RentZoobi 1. Open **Partner feeds** in the destination organization and choose the intended connection. Only an organization owner can manage it. 2. Under **Collect a hosted feed**, select the approved Rentari source. Confirm the displayed URL and server-access status. 3. Choose manual collection, or enable a schedule with an interval from 60 to 1,440 minutes. Confirm your identity to save the settings. A collection worker must be configured and running for scheduled work; saving settings alone does not start it. 4. Use **Collect feed now**. Review the last result and follow **Review latest collected delivery**. The collector stages new content; it does not apply or publish it. 5. Correct invalid rows at the source. An owner reviews and applies ready rows in RentZoobi, then completes photos, listing authority, moderation and publication requirements through the normal listing workflow. The collector accepts only approved HTTPS sources. Redirects, private-network destinations, oversized responses and compressed responses are rejected. Authentication is server-to-server; no source credential is returned to the browser. Contact support to update a rotated source credential in the secret manager. ## Changes and recovery | Result | Next action | |---|---| | Changes received for review | Open the staged receipt and inspect every row before applying. | | No new feed content | The current snapshot was already received. Existing receipts remain available. | | No eligible listings returned | Review the Rentari source scope and opt-ins. An empty response does not remove RentZoobi listings. | | Refresh needs attention | Record the safe error code and attempt time; ask support to check source reachability, access and XML. Keep credentials out of the message. | | Schedule saved; collection unavailable | Confirm environment activation and worker configuration. Repeated clicks do not enable a disabled service. | - **Pause scheduled collection** stops future scheduled pulls. It preserves the source, existing receipts and listings. You can review existing data while collection is paused. - Source changes do not automatically overwrite a newer owner edit. Resolve receipt conflicts and revise the source so its exporter produces a current snapshot with a higher sequence before applying. Re-collecting unchanged bytes and sequence returns the existing receipt, including its conflicts; it does not silently revalidate or overwrite the destination. - Withdrawal application can remove the mapped listing from public discovery. It does not delete the property, messages, applications or financial history. - Feed withdrawal and consent changes must be delivered and applied; disconnecting access alone is not a confirmed takedown. For an urgent removal, use the normal owner listing controls and notify support. - XML v1 does not import remote photo or floor-plan files. Complete authorized media through RentZoobi’s existing upload workflow. See [troubleshooting](troubleshooting.md) for intake errors and support evidence. This connection does not activate paid promotion, combine product subscriptions or establish certification with another listing network.