Method: accounts.accountLinks.patch

  • This document outlines how to update the account link target of an account link using a PATCH HTTP request.

  • The request uses a specific URL format including the account link name as a path parameter.

  • A required updateMask query parameter specifies that only the accountLinkTarget field can be updated.

  • The request and response bodies contain instances of the AccountLink resource.

  • The request requires authorization with the https://www.googleapis.com/auth/travelpartner OAuth scope.

Updates the account link target of an account link.

HTTP request

PATCH https://travelpartner.googleapis.com/v3/{accountLink.name=accounts/*/accountLinks/*}

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
accountLink.name

string

The resource name for the account link in the format accounts/{account_id}/accountLinks/{account_link_id}.

Query parameters

Parameters
updateMask

string (FieldMask format)

Required. The field to update. Only the accountLinkTarget field can be updated. Use the syntax shown in the example URL below and provide the new value in the request body.

Example request URL and request body:

PATCH https://travelpartner.googleapis.com/v3/accounts/123456789/
accountLinks/0123456789?updateMask=accountLink.account_link_target

 {
   "accountLinkTarget": {
     "hotelList": {
       "partnerHotelIds": ["1234", "4321"]
     }
   }
 }

The response body will only include the name field of an AccountLink.

The information above is sufficient for forming the URL and request body. The sentence below is auto-generated, supplemental information about the FieldMask format in general.

This is a comma-separated list of fully qualified names of fields. Example: "user.displayName,photo".

Request body

The request body contains an instance of AccountLink.

Response body

If successful, the response body contains an instance of AccountLink.

Authorization scopes

Requires the following OAuth scope:

  • https://www.googleapis.com/auth/travelpartner

For more information, see the OAuth 2.0 Overview.