Can HumDay connect to Reference Ideal Postcodes?

Yes. HumDay reads Reference Ideal Postcodes's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 26 operations are documented.

Do I need to write code to automate Reference Ideal Postcodes?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Reference Ideal Postcodes account.

What can HumDay do in Reference Ideal Postcodes?

7 of the 26 documented operations change something in Reference Ideal Postcodes, and 19 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Reference Ideal Postcodes account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Reference Ideal Postcodes is held behind that approval.

Automate Reference Ideal Postcodes

HumDay reads Reference Ideal Postcodes’s own published API description and derives 26 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Reference Ideal Postcodes is

# Getting Started ## Overview ### Access All API methods are either a `GET`, `POST` or `OPTIONS` request. The API communicates over both HTTPS and plain HTTP using IPv4 and IPv6. We recommend using HTTPS only although HTTP is available. We use appropriate HTTP status codes where possible to indicate the request status. ### Rate Limiting Each IP address is rate limited at 30 requests per second. Tr

API host: api.ideal-postcodes.co.uk

What HumDay can do in Reference Ideal Postcodes

7 documented operations change something in Reference Ideal Postcodes.

POSTCreate/keys/{key}/configs
POSTCreate/keys/{key}/licensees
POSTCleanse/cleanse/addresses
DELETEDelete/keys/{key}/configs/{config}
POSTUpdate/keys/{key}/configs/{config}
DELETECancel/keys/{key}/licensees/{licensee}
PUTUpdate/keys/{key}/licensees/{licensee}

What HumDay can read from Reference Ideal Postcodes

These are the operations a schedule or a trigger can watch.

GETEmail Validation/emails
GETFind Place/places
GETFind Address/autocomplete/addresses
GETResolve Place/places/${place}
GETExtract Addresses/addresses
GETList/keys/{key}/configs
GETPhone Number Validation/phone_numbers
GETList/keys/{key}/licensees
GETAvailability/keys/{key}
GETRetrieve by UDPRN/udprn/{udprn}
GETRetrieve by UMPRN/umprn/{umprn}
GETResolve Address (GBR)/autocomplete/addresses/{address}/gbr
GETResolve Address (USA)/autocomplete/addresses/{address}/usa
GETLookup Postcode/postcodes/{postcode}
GETUsage Stats/keys/{key}/usage
GETDetails/keys/{key}/details
GETLogs (CSV)/keys/{key}/lookups
GETRetrieve/keys/{key}/configs/{config}
GETRetrieve/keys/{key}/licensees/{licensee}

How automating Reference Ideal Postcodes works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Reference Ideal Postcodes account.
Grant access, then go live. You approve the specific Reference Ideal Postcodes operations it may use — and only those.