AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Manage google contacts1/20/2024 Issued tokens are valid for 29 days, and the REPORT ClientĪpplications must store this value and issue periodic sync-collection REPORT requests to determine changes since the last issued Client programs use the sync-token PROPFIND request on the Addressīook to obtain the sync-token representing its current state.Getctag property will result in throttling. Should store this value and use it only on the initial sync and as aįallback when a sync-token is invalidated. Is guaranteed to change if any contact changes. Therefore whether a synchronization is needed. Resource to determine if any contact has changed on the server and Client programs use the getctag PROPFIND request on the Address Book.These are the main operations used by client Should look for the details in the relevant RFC. The following is a general description of the operations supported. Rather, the resources should be discovered The structure mayĬhange and must not be hardcoded. The current URI structure is specified here to helpĭevelopers understand the concepts in the following section. Client applications act on resources that areĭesignated by their URIs. Google recommends a rate of every 2-4 weeks. URI discovery periodically to verify if the cached path is still up to date and The well-known URI must not be permanently cached (as per The redirect path returned in the HTTP 301 response through a PROPFIND on Performing a PROPFIND on the addressbook-home-set and looking for theĪddressbook and collection resources. Your client program can then discover the principal address book by Once redirected ( HTTP 301) to an Address Book Resource, your client programĬan then perform a PROPFIND on it to discover theĭAV:current-user-principal, DAV:principal-URL, and addressbook-home-set To use CardDAV, your client program must initially connect to the canonicalĭiscovery path by performing an HTTP PROPFIND on: Any attempt to connect over HTTP with Basic authentication or withĪn email/password that doesn't match a Google account results in an HTTP The CardDAV server will notĪuthenticate a request unless it arrives over HTTPS with OAuth 2.0Īuthentication of a Google account, and your application is registered onĭevConsole. You must not hardcode any URI as they could change at any time.Ĭlient applications must use HTTPS, and OAuth 2.0 authentication must be The CardDAV protocol allows discovery of the address book and contact resources Using OAuth 2.0 for Installed Applications.Refer to the linkedĭocumentation below for information on using OAuth 2.0 to access Google APIs: Google’s CardDAV interface requires OAuth 2.0. Google uses VCard 3.0 as the contact encoding format.That it does not need to synchronize any changed contacts. This allows the client program to quickly determine The contactsĬtag is like a resource ETag it changes when anything in the contactĪddress book has changed. Which is shared between the CardDAV and CalDAV specifications. Bootstrapping of CardDAV URLs must take place according to section 6 ofĬaldav-ctag-02: Calendar Collection Entity Tag (CTag) in CalDAV,.rfc6764: Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV).Google does not support any other authentication method.įor security of contact data, we require CardDAV connections to use Supports authenticating CardDAV client programs using OAuth 2.0 HTTPĪuthentication.Rfc6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage rfc6749: The OAuth 2.0 Authorization Framework and.Client applications must switch to this mode of operation after the.rfc6578: Collection Synchronization for WebDAV.Supports providing a principal collection and a contacts collection.Supports the HTTP method REPORT, but not all defined reports are.rfc6352: CardDAV: vCard Extensions to Web Distributed Authoring and.Supports creating new contacts without specifying an ID.rfc5995: Using POST to Add Members to WebDAV Collections.Does not support WebDAV Access Control (rfc3744).Does not support arbitrary (user-defined) WebDAV properties.Does not support the HTTP methods LOCK, UNLOCK, COPY, MOVE, or.Supports the HTTP methods GET, PUT, DELETE, OPTIONS, and.rfc2518: HTTP Extensions for Distributed Authoring (WebDAV).The full specification is not implemented, but many clients such asįor each relevant specification, Google's CardDAV support is as follows: Your client application can use the CardDAV API toĬreate new contacts, edit or delete existing contacts, and query for contacts You can view and manage your contacts using Google's CardDAV protocol.Ĭontacts are stored in the user's Google Account most Google services haveĪccess to the contact list.
0 Comments
Read More
Leave a Reply. |