AI-generated Key Takeaways
-
Permanently deletes a specific product input from your Merchant Center account using a DELETE request.
-
Requires specifying the product input's name in the URL path, including account, channel, content language, feed label, and offer ID.
-
Needs the data source (primary or supplemental) to be identified in the query parameters for targeted deletion.
-
Utilizes OAuth 2.0 for authorization and mandates the
https://www.googleapis.com/auth/contentscope for access. -
Changes may take several minutes to reflect and retrieve the processed product after the deletion.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
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.
HTTP request
DELETE https://merchantapi.googleapis.com/products/v1beta/{name=accounts/*/productInputs/*}
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
name |
Required. The name of the product input to delete. Format: The {productInput} segment is a unique identifier for the product. This identifier must be unique within a merchant account and generally follows the structure: The format of the {productInput} segment in the URL is automatically detected by the server, supporting two options:
We recommend using the Encoded Format for all product IDs to ensure correct parsing, especially those containing special characters. The presence of tilde ( Note: For calls to the v1beta version, the plain format is |
Query parameters
| Parameters | |
|---|---|
dataSource |
Required. The primary or supplemental data source from which the product input should be deleted. Format: |
Request body
The request body must be empty.
Response body
If successful, the response body is an empty JSON object.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/content
For more information, see the OAuth 2.0 Overview.