• Added the POST /credit_allocation endpoint for allocating credits to client accounts
• Updated the POST /client endpoint to optionally set the new client's Auto-Renew settings and initial pack size
• Changed the POST /client endpoint to immediately activate the new client by default

• Adds new page for Embedded Tech API
• Remove old BigCommerce AAC v1 script
• Automatically invalidate CloudFront cache during deploy pipeline
• Upgrades VuePress and Node to more recent versions

• Updated pipeline to use per app/environment credentials instead of per account for Shopify deployment
• Upgraded Shopify app to the latest Shopify recommended technologies (remix + vite)
• Upgraded Shopify checkout extensions to the latest recommended technologies (polaris web ui)
• Updated Shopify API version

• Added a config option to disable plus-four codes for US ZIP codes
• Fixed a bug where Postcode Lookup would be broken on the Edit Order admin page

Fetchify website: LIVE

Magento Marketplace: submitted, awaiting review

Composer: not yet available

• New: API now returns more detailed client pack and usage data
• Improved: New client/token creation immediately activated  (previously required a 15 mins separate sync)

UKPCLU has been updated with the latest PAF data from Royal Mail.

• Style fixes for AAC
• Added option to exclude +4 from US zip codes
• Pinned CSS version to lock to the correct release

Bug Fixes

• Fixed an issue where the access token for a new client account created via the Embedded Tech API was not immediately accessible. Tokens are now generated using the same process as the admin portal, so they're fully active and usable as soon as the account is created.
• Note : Token becomes available 15 mins after creation

No action is required to receive this update — it is live on the API now.

What's New

A new Embedded Tech API reference page is now live on the Fetchify docs site, covering the Account Automation API partners use to create and manage sub-client accounts programmatically.

The page includes:

• Getting started — partner account and API key requirements, and where to generate a Partner API key
• Authentication — using your Partner API key as a Bearer token
• GET /client — list and page through your client accounts, with query parameters and example request/response
• POST /client — create a new sub-client account, including the access token returned for that client
• Common use cases (auto-provisioning on signup, syncing client lists, usage monitoring) and a support contact

From 1 September 2026, Fetchify's UK Postcode Lookup service is moving to two new dedicated IP addresses. 

Does this affect you? 

If you whitelist IPs to connect to Fetchify for UK Postcode Lookup, you'll need to update your settings before 1 September 2026. 

Address Autocomplete, Phone Validation, Email Validation, and Bank Validation are unaffected by this change and continue to use their existing IP addresses (18.169.116.40 and 52.26.48.26). 

If you don't restrict access by IP address, no action is needed.

What's changing 

We're retiring the broad range of shared AWS IP addresses currently in use and replacing them with two static IPs used exclusively by Fetchify. 

This means: 

• Enhanced security - you'll only need to whitelist two specific IPs dedicated exclusively to Fetchify, replacing the previous broad set of shared AWS IPs.  
• Higher availability - the new setup spans two regions (US and EU) with load balancing, enabling automatic failover if there is a server issue.  
• Improved performance - requests are automatically routed to the nearest server for faster response times. 

What this means for you 

If your organisation whitelists specific IPs to connect to Fetchify UK Postcode lookup and doesn't update in time, your connection to our UK Postcode Lookup will stop working on 1 September 2026. In practice, this means any postcode lookup on your website, checkout, or internal systems that rely on this service will stop returning results, and your team or customers will need to type addresses in manually until your whitelist is updated. 

What you need to do 

Add these two new addresses to your firewall whitelist before 1 September 2026, while keeping your existing CloudFront IP range whitelisted:  

• 166.117.21.17  
• 76.223.67.27  

Important

Do not remove your existing CloudFront IP range before 1 September 2026. Both must be whitelisted at the same time during the transition.  

From 8 September 2026, you can remove the old CloudFront IP range, so that only the two new addresses above remain whitelisted. 

Need help? 

If you're unsure whether this affects you or need help making the change, contact [email protected].