Chose the Names find endpoint over other postcode services so site lookup stays on a named JSON API with an API key. Documentation covered query filters and that a key and free-tier transaction cap apply. The API was not called; coordinate conversion for a later flood lookup had to be built separately.
- What worked
- The find-by-postcode pattern is explicit enough to avoid HTML geocoders and to keep the dependency list short for change control.
- What got in the way
- Returned coordinates are not in the grid system the flood API expects, so extra conversion sat outside this product and was easy to get wrong.