Google Address Validation

Install corsair and @corsair-dev/googleaddressvalidation, add the Google Address Validation plugin, and connect with an API key. Then call methods like corsair.googleaddressvalidation.api.address.provideFeedback() from your app. Corsair keeps each tenant isolated.

Yes. Google Address Validation requires an API key from your Google Address Validation account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Google Address Validation, GitHub, Notion, Stripe, and the rest. Trigger Google Address Validation from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for google api for validating, standardizing, and geocoding postal addresses worldwide. Common builds include sync jobs, admin tooling, and agents that call Google Address Validation APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Google Address Validation API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/googleaddressvalidation in the open repo. When Google Address Validation ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Google Address Validation data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Google Address Validation data on your behalf.