Merchant API (merchantapi:products_v1)

2025-11-11

3 updated methods

Updates

    Methods
  • merchantapi.accounts.productInputs.patch

      Parameters :

        productIdBase64UrlEncoded

          Description : Optional. If true, the `{productInput}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{productInput}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.

          Location : query

          Type : boolean

  • merchantapi.accounts.productInputs.delete

      Parameters :

        productIdBase64UrlEncoded

          Description : Optional. If true, the `{productInput}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{productInput}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.

          Location : query

          Type : boolean

  • merchantapi.accounts.products.get

      Parameters :

        productIdBase64UrlEncoded

          Description : Optional. If true, the `{product}` in the `name` field of the request will be interpreted as unpadded base64url-encoded and decoded during request processing to match the decoded value. Default value is `false`. Use this if your `{product}` contains special characters, such as forward slash `/` or other characters that are unpadded base64url-encoded (as per RFC 7515: https://datatracker.ietf.org/doc/html/rfc7515#section-2). Note that future versions of the API will only accept unpadded base64url-encoded product ids, so we strongly recommend proactively setting this to `true` and encoding the product ids.

          Location : query

          Type : boolean