Connect your portal feed credentials

Portal distribution runs on credentials the portal issues to you. They belong to your agency, not to us, and they stay yours if you leave.

What this does

Stores your feed credentials against your tenancy and lets the platform publish listings under your own agency identifier.

How to do it

1. Ask each portal for your feed credentials if you do not already hold them. They will ask which software you are moving to and may want a short notice period.
2. In the tenant admin, open Feeds and add one entry per portal. Each entry takes the agency identifier and the credential the portal gave you.
3. Publish one listing in test mode. The platform sends it and waits for the portal to answer.

What proves it worked

The feed status screen shows the acknowledgement the portal returned, with the time it arrived and the identifier the portal echoed back. That is the observable. A credential that saved without error proves you typed something; an acknowledgement proves the portal accepted it.

Check the identifier in the acknowledgement matches your agency. A credential that belongs to another office in your group will authenticate cleanly and publish your listing under their name.

When it does not work

If a portal returns nothing at all, the credential is usually correct and the feed is not yet switched on at their end. Portals commonly provision the credential first and enable the feed on a later date. The status screen distinguishes those two states rather than showing both as an error, because they need different phone calls.

If a portal returns a rejection, the message it sent is shown in full. We do not summarise it, because the useful detail is usually in the part a summary would drop.

What the status screen will not do

It will not show a green state for a feed it has not heard from. A feed that has gone quiet reads as quiet, with the time of the last acknowledgement, rather than as healthy. Those are different sentences and only one of them is true.