Update contact data for an existing contact person. Any non-contact data will not be modified. Any non-contact data in the person to update will be ignored. All fields specified in the update_mask
will be replaced. The server returns a 400 error if person.metadata.sources
is not specified for the contact to be updated or if there is no contact source. The server returns a 400 error with reason "failedPrecondition"
if person.metadata.sources.etag
is different than the contact's etag, which indicates the contact has changed since its data was read. Clients should get the latest person and merge their updates into the latest person. The server returns a 400 error if memberships
are being updated and there are no contact group memberships specified on the person. The server returns a 400 error if more than one field is specified on a field that is a singleton for contact sources: * biographies * birthdays * genders * names Mutate requests for the same user should be sent sequentially to avoid increased latency and failures.
Scopes
You will need authorization for the https://www.googleapis.com/auth/contacts scope to make a valid call.
If unset, the scope for this method defaults to https://www.googleapis.com/auth/contacts.
You can set the scope for this method like this: people1 --scope <scope> people update-contact ...
Required Scalar Argument
- <resource-name> (string)
- The resource name for the person, assigned by the server. An ASCII string in the form of
people/{person_id}
.
- The resource name for the person, assigned by the server. An ASCII string in the form of
Required Request Value
The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure. In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.
For example, a structure like this:
Person:
age-range: string
etag: string
metadata:
deleted: boolean
linked-people-resource-names: [string]
object-type: string
previous-resource-names: [string]
resource-name: string
can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.
-r . age-range=stet
- Output only. DEPRECATED (Please use
person.ageRanges
instead) The person's age range.
- Output only. DEPRECATED (Please use
etag=kasd
- The HTTP entity tag of the resource. Used for web cache validation.
metadata deleted=true
- Output only. True if the person resource has been deleted. Populated only for
people.connections.list
andotherContacts.list
sync requests.
- Output only. True if the person resource has been deleted. Populated only for
linked-people-resource-names=et
- Output only. Resource names of people linked to this resource.
- Each invocation of this argument appends the given value to the array.
object-type=et
- Output only. DEPRECATED (Please use
person.metadata.sources.profileMetadata.objectType
instead) The type of the person object.
- Output only. DEPRECATED (Please use
-
previous-resource-names=vero
- Output only. Any former resource names this person has had. Populated only for
people.connections.list
requests that include a sync token. The resource name may change when adding or removing fields that link a contact and profile such as a verified email, verified phone number, or profile URL. - Each invocation of this argument appends the given value to the array.
- Output only. Any former resource names this person has had. Populated only for
-
.. resource-name=erat
- The resource name for the person, assigned by the server. An ASCII string in the form of
people/{person_id}
.
- The resource name for the person, assigned by the server. An ASCII string in the form of
About Cursors
The cursor position is key to comfortably set complex nested structures. The following rules apply:
- The cursor position is always set relative to the current one, unless the field name starts with the
.
character. Fields can be nested such as in-r f.s.o
. - The cursor position is set relative to the top-level structure if it starts with
.
, e.g.-r .s.s
- You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify
-r struct.sub_struct=bar
. - You can move the cursor one level up by using
..
. Each additional.
moves it up one additional level. E.g....
would go three levels up.
Optional Output Flags
The method's return value a JSON encoded structure, which will be written to standard output by default.
- -o out
- out specifies the destination to which to write the server's result to.
It will be a JSON-encoded structure.
The destination may be
-
to indicate standard output, or a filepath that is to contain the received bytes. If unset, it defaults to standard output.
- out specifies the destination to which to write the server's result to.
It will be a JSON-encoded structure.
The destination may be
Optional Method Properties
You may set the following properties to further configure the call. Please note that -p
is followed by one
or more key-value-pairs, and is called like this -p k1=v1 k2=v2
even though the listing below repeats the
-p
for completeness.
-
-p person-fields=string
- Optional. A field mask to restrict which fields on each person are returned. Multiple fields can be specified by separating them with commas. Defaults to all fields if not set. Valid values are: * addresses * ageRanges * biographies * birthdays * calendarUrls * clientData * coverPhotos * emailAddresses * events * externalIds * genders * imClients * interests * locales * locations * memberships * metadata * miscKeywords * names * nicknames * occupations * organizations * phoneNumbers * photos * relations * sipAddresses * skills * urls * userDefined
-
-p sources=string
- Optional. A mask of what source types to return. Defaults to READ_SOURCE_TYPE_CONTACT and READ_SOURCE_TYPE_PROFILE if not set.
-
-p update-person-fields=string
- Required. A field mask to restrict which fields on the person are updated. Multiple fields can be specified by separating them with commas. All updated fields will be replaced. Valid values are: * addresses * biographies * birthdays * calendarUrls * clientData * emailAddresses * events * externalIds * genders * imClients * interests * locales * locations * memberships * miscKeywords * names * nicknames * occupations * organizations * phoneNumbers * relations * sipAddresses * urls * userDefined
Optional General Properties
The following properties can configure any call, and are not specific to this method.
-
-p $-xgafv=string
- V1 error format.
-
-p access-token=string
- OAuth access token.
-
-p alt=string
- Data format for response.
-
-p callback=string
- JSONP
-
-p fields=string
- Selector specifying which fields to include in a partial response.
-
-p key=string
- API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
-
-p oauth-token=string
- OAuth 2.0 token for the current user.
-
-p pretty-print=boolean
- Returns response with indentations and line breaks.
-
-p quota-user=string
- Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
-
-p upload-type=string
- Legacy upload protocol for media (e.g. "media", "multipart").
-
-p upload-protocol=string
- Upload protocol for media (e.g. "raw", "multipart").