ApivomApivom
Get Demo

Google Address Validation API Connector

Google's Address Validation API — parse, standardise, geocode and verify a postal address down to the component level, with CASS certification for US mail — registered in Apivom Atlas for Apivom tenants that want clean, deliverable addresses on customer and shipping records, with your own Maps Platform key.

What you can do

  • Validate an address: component-level verdicts (confirmed, inferred, unconfirmed), corrected formatting and a geocode
  • US addresses with USPS CASS processing; address metadata such as residential vs business and PO box
  • Provide validation feedback so Google learns which suggestion your user finally accepted
  • Two routes registered in Atlas with the credential contract and the AI integration guide (llms.txt)

Use cases

  • Catch bad addresses at entry — Validate the shipping or billing address when a company or contact is created and show the corrected version for confirmation before it is saved.
  • Clean an existing customer base — Run the API over imported records to standardise formatting and flag undeliverable addresses before a mailing or a field campaign.

The Address Validation API on addressvalidation.googleapis.com takes an address as typed and returns a verdict: which components Google could confirm, which it inferred or corrected, which remain unconfirmed, plus a standardised formatting, a geocode and metadata such as whether the address is residential or a PO box. For the United States it includes USPS CASS processing, which is what mailing operations need for deliverability. A second route lets you report back which of Google's suggestions the user accepted. Apivom Atlas registers both routes with the Maps Platform credential contract, per-tenant logging and the published llms.txt guide; your key, your Google Cloud project and its quotas apply. No Apivom product workflow validates addresses through it today — it is available for your own forms and batch clean-ups, and wiring it into a product flow is scoped per customer.

Authentication

Your own Google Cloud API key (Maps Platform) with this API enabled on the project; the Apivom product sends it as the x-goog-api-key header on each call. Google bills the project that owns the key. The key is encrypted in your Iris tenant; Apivom Atlas stores nothing.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Which countries are covered?

Google publishes the supported-regions list for Address Validation; coverage is strongest for North America and Western Europe and growing. CASS-certified processing applies to US addresses only.

Which Google Cloud project pays for the calls?

The project that owns the API key you connect. Enable this specific API on that project, restrict the key to the APIs you actually use, and Google's Maps Platform pricing and monthly credit apply to it directly — Apivom adds no charge and shows every call in your tenant's integration log.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.