Class AccountsResource.ProductInputsResource
The "productInputs" collection of methods.
Inheritance
AccountsResource.ProductInputsResource
Assembly: Google.Apis.Merchant.products_v1.dll
public class AccountsResource.ProductInputsResource
Constructors
Constructs a new resource.
Declaration
public ProductInputsResource(IClientService service)
Parameters
Methods
Deletes a product input from your Merchant Center account. After inserting, updating, or deleting a
product input, it may take several minutes before the processed product can be retrieved.
Declaration
public virtual AccountsResource.ProductInputsResource.DeleteRequest Delete(string name)
Parameters
| Type |
Name |
Description |
| string |
name |
Required. The name of the product input to delete. Format:
accounts/{account}/productInputs/{productInput} The {productInput} segment is a unique identifier for
the product. This identifier must be unique within a merchant account and generally follows the
structure: content_language~feed_label~offer_id. Example: en~US~sku123 For legacy local products,
the structure is: local~content_language~feed_label~offer_id. Example: local~en~US~sku123 The format
of the {productInput} segment in the URL is automatically detected by the server, supporting two
options: 1. Encoded Format: The {productInput} segment is an unpadded base64url encoded string
(RFC 4648 Section 5). The decoded string must result in the content_language~feed_label~offer_id
structure. This encoding MUST be used if any part of the product identifier (like offer_id) contains
characters such as /, %, or ~. * Example: To represent the product ID en~US~sku/123, the
{productInput} segment must be the base64url encoding of this string, which is ZW5-VVMtc2t1LzEyMw.
The full resource name for the product would be accounts/123/productInputs/ZW5-VVMtc2t1LzEyMw. 2.
Plain Format: The {productInput} segment is the tilde-separated string
content_language~feed_label~offer_id. This format is suitable only when content_language,
feed_label, and offer_id do not contain URL-problematic characters like /, %, or ~. We
recommend using the Encoded Format for all product IDs to ensure correct parsing, especially those
containing special characters. The presence of tilde (~) characters in the {productInput} segment is
used to differentiate between the two formats. Note: For calls to the v1beta version, the plain format
is channel~content_language~feed_label~offer_id, for example:
accounts/123/productinputs/online~en~US~sku123.
|
Returns
Uploads a product input to your Merchant Center
account. You must have a products data
source to be able to insert a
product. The unique identifier of the data source is passed as a query parameter in the request URL. If
a product input with the same contentLanguage, offerId, and dataSource already exists, then the product
input inserted by this method replaces that entry. After inserting, updating, or deleting a product
input, it may take several minutes before the processed product can be retrieved.
Declaration
public virtual AccountsResource.ProductInputsResource.InsertRequest Insert(ProductInput body, string parent)
Parameters
| Type |
Name |
Description |
| ProductInput |
body |
The body of the request.
|
| string |
parent |
Required. The account where this product will be inserted. Format: accounts/{account}
|
Returns
Updates the existing product input in your Merchant Center account. The name of the product input to
update is taken from the name field within the ProductInput resource. After inserting, updating, or
deleting a product input, it may take several minutes before the processed product can be retrieved.
Declaration
public virtual AccountsResource.ProductInputsResource.PatchRequest Patch(ProductInput body, string name)
Parameters
| Type |
Name |
Description |
| ProductInput |
body |
The body of the request.
|
| string |
name |
Identifier. The name of the product. Format: accounts/{account}/productInputs/{productinput} The
{productinput} segment is a unique identifier for the product. This identifier must be unique within a
merchant account and generally follows the structure: content_language~feed_label~offer_id. Example:
en~US~sku123 For legacy local products, the structure is:
local~content_language~feed_label~offer_id. Example: local~en~US~sku123 The format of the
{productinput} segment in the URL is automatically detected by the server, supporting two options: 1.
Encoded Format: The {productinput} segment is an unpadded base64url encoded string (RFC 4648
Section 5). The decoded string must result in the content_language~feed_label~offer_id structure. This
encoding MUST be used if any part of the product identifier (like offer_id) contains characters such
as /, %, or ~. * Example: To represent the product ID en~US~sku/123, the {productinput}
segment must be the base64url encoding of this string, which is ZW5-VVMtc2t1LzEyMw. The full resource
name for the product would be accounts/123/productinputs/ZW5-VVMtc2t1LzEyMw. 2. Plain Format: The
{productinput} segment is the tilde-separated string content_language~feed_label~offer_id. This
format is suitable only when content_language, feed_label, and offer_id do not contain
URL-problematic characters like /, %, or ~. We recommend using the Encoded Format for all
product IDs to ensure correct parsing, especially those containing special characters. The presence of
tilde (~) characters in the {productinput} segment is used to differentiate between the two formats.
Note: For calls to the v1beta version, the plain format is
channel~content_language~feed_label~offer_id, for example:
accounts/123/productinputs/online~en~US~sku123.
|
Returns