Troubleshoot
When working with shared contacts, you might encounter the following issues.
Firewall issues
If your firewall blocks HTTP PUT messages, include an X-HTTP-Method-Override:
PUT header in a POST request. For more information, see
Google Data API protocol basics.
If your firewall blocks HTTP DELETE messages, include an
X-HTTP-Method-Override: DELETEheader in a POST request. For more
information, see
Google Data API protocol basics.
Limits
The following summarizes the constraints that apply to the Domain Shared Contacts API:
- A single shared contact list can contain up to 200,000 entries.
- A single shared contact can contain up to 2KB of data. The total
XML that represents the shared contact can be larger than 2KB.
- A response is truncated if it exceeds 10MB in length.
- One batch request can include up to 100 operations.
- Changes can take up to 24 hours to be reflected in the email address
autocomplete and the contact manager.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-12-19 UTC.
[null,null,["Last updated 2024-12-19 UTC."],[[["When using shared contacts, firewall issues may arise requiring the use of `X-HTTP-Method-Override` headers in `POST` requests for `PUT` and `DELETE` operations."],["Shared contact lists have limits, including a maximum of 200,000 entries per list, 2KB of data per contact, and response truncations at 10MB."],["Batch requests are limited to 100 operations and changes may take up to 24 hours to be fully reflected in systems."]]],["Firewall restrictions on HTTP `PUT` or `DELETE` messages can be bypassed by including `X-HTTP-Method-Override: PUT` or `X-HTTP-Method-Override: DELETE` headers, respectively, within a `POST` request. The Domain Shared Contacts API has limits: 200,000 entries per list, 2KB per contact (excluding XML overhead), 10MB response truncation, 100 operations per batch, and a 24-hour delay for changes to propagate.\n"]]
