Managing portal feeds

When you access your Zoopla feeds you'll be presented with a table highlighting any existing feeds that you have setup and the ability to create a new feed:

You can have an unlimited number of exports setup at any one time.

Adding and editing a new portal feed

To set up a new export click the 'Add new portal' button.

To edit an existing portal feed click the 'Edit' button next to the export in question.

You'll be presented with the ability to add/edit the portal feed with the settings explained below:

Portal details

Name - Give the feed an internal name (e.g. 'Zoopla') so you have some way to differentiate between them. Especially useful if setting up multiple portal feeds.

Mode - Whether the feed is live or not. The options here are:

i) Off - The feed is completely inactive. No properties are sent and the feed doesn't show anywhere throughout Property Hive

ii) Test - You can select properties to be sent to the portal, but no properties will actually be sent.

'Test' mode here does not mean properties will be sent to the test version of the portals site.

If the third party requires you to send properties to testing/staging/sandbox site before going live, you would control this using the 'API URLs' (see below) but 'Mode' will need to be 'Live'.

iii) Live - Properties saved in Property Hive are sent to the third party.

Overseas - The Zoopla format has a UK schema, and an overseas schema. If you're sending properties outside of the UK this checkbox should be ticked.

Certificate details

In order to authenticate that requests to send and remove properties are genuine, and to prevent anybody just submitting properties on your behalf, there is a layer of authentication involved.

In the Zoopla format this authentication is done in the form of a certificate and a private key.

Please see more about certificates and the processes involved in our dedicated 'Generating and obtaining certificates' guide.


We need to know the API URLs that should be used when sending and removing properties.

The portal in question will send these to you, however we include the most common ones in the tooltip as well for you to copy and paste.

Note how there different API URLs for 'Test' vs 'Live'. This means when the feed is approved and you're ready to go live, you'll need to edit the feed and change the API URL's accordingly here.

Branch codes

These will be provided by the third party portal.

The branch codes might be the same for both sales and lettings but can also differ. If it's the same you can simply enter the same branch code for both sales and lettings as per the screenshot above.

Advanced settings

Only send property if different from last time sent - By default a property will be sent to the portal each time it is saved. Most of the time the data might remain unchanged thus causing unnecessary requests to be sent.

Select this option if we should only send the property if the data has changed since last time it was sent.

This is especially applicable if importing properties AND sending them in real-time feeds, otherwise you can probably leave this unticked.

Unique property ID - We need a unique property identifier to link a property in Property Hive to the same property on the portal.

We recommend using the 'WordPress Post ID' as this will always be unique. However, if you wish to use the reference number entered on the property record you must ensure:

a) a reference number has been entered

b) it is completely unique

Changing this option once properties have already been sent will result in them being seen as completely new properties.

Please check with the third party portal before changing this option.

You will also need to re-push all properties.