Contacts
Google Contacts API
Contacts and autocomplete from a connected Google account
Google Contacts
Contacts
How an account links
- OAuth
- contactsContacts · Contact search2
- platformWebhooks1
What Aux0 does with Google Contacts
3 capabilitiesContacts and autocomplete from a connected Google account
Read the contacts on a connected Google account, including the addresses Google collects automatically from mail. This is what makes recipient autocomplete feel instant in a mail client built on Aux0.
Contacts
- ContactsPage through the contacts on the account, with addresses and phones.
GET /v1/contacts - Contact searchLook up a contact by name or address, for autocomplete.
GET /v1/contacts/search
Platform
- WebhooksSigned delivery of every event, with replay and a dead letter queue.
POST /v1/webhooks
How an account is linked
AuthOAuth
The provider's own consent screen. Your user signs in where they expect to, grants the scopes you asked for, and comes back. No credential passes through Aux0 at all.
Whichever method a provider uses, your users complete it on a page Aux0 serves under your branding. You receive an account id and a webhook; no password, QR scan or one-time code ever reaches your product. How hosted auth works.
What it is bought for
Use casesRecipient autocomplete in a mail composer
Resolving a sender to a known person
What you should know first
LimitsThe constraints, before you commit
These are the provider's rules, not ours. We would rather you read them now than discover one in production.
Automatically collected addresses need their own scope and are read-only.
Next
RelatedConnect Google Contacts on the free plan
One connected account, every provider, forever. It is enough to build the whole integration before you pay for anything.