Skip to content
Screaming Data
Documentation menu

Amazon Monitoring API

Add products to monitoring

Add products once and receive fresh observations hourly, every 6 hours or daily.

POST
https://api.screamingdata.dev/v1/amazon/monitoring/add
Authentication
API key (HTTP Basic)
Cost
  • $0.0006 per observation

List price · volume rates on request

Body
Array of up to 100 tasks

Overview

Adds each product in the array to your monitoring: it is observed regularly at the chosen frequency. New observations appear in monitoring/list and in history.

Adding the same ASIN and marketplace again updates the frequency and tag of the existing subscription instead of creating a duplicate.

Every delivered observation is charged at your monitoring rate. If your balance cannot cover an observation, your subscriptions switch to paused_balance and resume automatically once balance is added. A subscription added while your balance is below the monitoring rate, or while your subscriptions are paused, starts as paused_balance and resumes in the same way.

An account can monitor up to 10,000 products; beyond that the task fails with 40000 — delete subscriptions you no longer need, or ask support for a higher limit.

Platforms that serve many end users can attribute subscriptions with external_user_id — an opaque id from your system. Do not put personal data in it: values that look like e-mail addresses are rejected.

Cost

Adding a subscription is free; each delivered observation is charged. List price: $0.0006 per delivered observation — volume rates on request; the charges appear in your usage. See pricing · Get a quote

Request

POST /v1/amazon/monitoring/add with Content-Type: application/json.

Body fields

The request body is a JSON array of 1–100 task objects. Each object has these fields:

asin
stringrequired

ASIN of the product. Case-insensitive; must be 10 letters or digits after uppercasing.

  • Pattern^[A-Z0-9]{10}$
  • ExampleB0EXAMPLE1
marketplace
stringrequired

Marketplace code. The aliases us and usa (for com) and gb (for uk) are also accepted. See Marketplaces.

  • Allowedcomukdefresitnlcaaujpmxin
  • Examplecom
frequency
stringrequired

How often to observe the product.

  • Allowedhourlyevery_6hdaily
  • Exampledaily
tag
stringoptional

Your own identifier. It is echoed back in the task data, returned with the subscription and can be used to filter monitoring/list.

  • Max length255 characters
  • Exampleclient-42
external_user_id
stringoptional

Opaque id of your own end user. Must not contain personal data; values that look like e-mail addresses are rejected.

  • Max length255 characters
  • Exampleu_8f3a2c

Request example

The examples read your credentials from the API_LOGIN and API_KEY environment variables.

curl --request POST \
  --url "https://api.screamingdata.dev/v1/amazon/monitoring/add" \
  --user "$API_LOGIN:$API_KEY" \
  --header "Content-Type: application/json" \
  --data '[
  {
    "asin": "B0EXAMPLE1",
    "marketplace": "com",
    "frequency": "daily",
    "tag": "client-42",
    "external_user_id": "u_8f3a2c"
  },
  {
    "asin": "B0EXAMPLE2",
    "marketplace": "uk",
    "frequency": "hourly",
    "tag": "launch-watch"
  }
]'

Response

HTTP 200. The body is the standard response envelope; check status_code at the top level and in every task.

Response example
{
  "version": "1.0.0",
  "status_code": 20000,
  "status_message": "Ok.",
  "time": "0.0268 sec.",
  "cost": 0,
  "tasks_count": 2,
  "tasks_error": 0,
  "tasks": [
    {
      "id": "09241302-3c9e-4f1a-8b2d-5e7a0c6f4d18",
      "status_code": 20000,
      "status_message": "Ok.",
      "time": "0.0051 sec.",
      "cost": 0,
      "result_count": 1,
      "path": [
        "v1",
        "amazon",
        "monitoring",
        "add"
      ],
      "data": {
        "api": "amazon",
        "function": "monitoring",
        "asin": "B0EXAMPLE1",
        "marketplace": "com",
        "frequency": "daily",
        "tag": "client-42",
        "external_user_id": "u_8f3a2c"
      },
      "result": [
        {
          "id": 3051,
          "asin": "B0EXAMPLE1",
          "marketplace": "com",
          "frequency": "daily",
          "tag": "client-42",
          "external_user_id": "u_8f3a2c",
          "status": "active",
          "created_at": "2026-09-24T13:02:11Z"
        }
      ]
    },
    {
      "id": "09241302-9a4b-4c7e-a1f3-2d8b6e0c5f39",
      "status_code": 20000,
      "status_message": "Ok.",
      "time": "0.0047 sec.",
      "cost": 0,
      "result_count": 1,
      "path": [
        "v1",
        "amazon",
        "monitoring",
        "add"
      ],
      "data": {
        "api": "amazon",
        "function": "monitoring",
        "asin": "B0EXAMPLE2",
        "marketplace": "uk",
        "frequency": "hourly",
        "tag": "launch-watch"
      },
      "result": [
        {
          "id": 3052,
          "asin": "B0EXAMPLE2",
          "marketplace": "uk",
          "frequency": "hourly",
          "tag": "launch-watch",
          "external_user_id": null,
          "status": "active",
          "created_at": "2026-09-24T13:02:11Z"
        }
      ]
    }
  ]
}

Result fields

Each element of tasks[].result is a subscription object. A monitored product. monitoring/add returns it without latest_observation.

id
integer

Subscription id. Use it with monitoring/delete.

asin
string

Monitored ASIN.

marketplace
string

Marketplace code.

frequency
string

hourly, every_6h or daily.

tag
string· nullable

Your tag.

external_user_id
string· nullable

Your opaque end-user id.

status
string

active, or paused_balance while the balance cannot cover observations (resumes automatically once balance is added).

created_at
string (date-time)

When the subscription was created, ISO 8601 in UTC.

latest_observation
object· nullable

The latest observation delivered to this subscription (a product object, same shape as in task_get), or null before the first delivery. Returned by monitoring/list only.

Status codes

Codes this endpoint can return, at the request or task level. See Status codes for handling advice.

CodeMessageHTTPLevelWhen
20000Ok.200Request / taskThe request, or the individual task, was processed successfully.
40000Bad Request.400 / 200Request / taskThe body is not valid JSON or does not have the expected shape (for example, not an array of task objects, or more than one task for live). Also returned with HTTP 413 for bodies larger than 1 MiB and with HTTP 405 for a wrong HTTP method. As a task-level code (HTTP 200) it means the task cannot be carried out as asked, for example because the account already has the maximum number of API keys or monitored products.
40001Too many tasks in one request (max 100).400RequestA POST body contains more task objects than allowed.
40100Authentication failed.401RequestThe Authorization header is missing or malformed, or the login and API key do not match.
40101API key revoked.401RequestThe API key was revoked. Use another active key or create a new one.
40102Account disabled.401RequestThe account is disabled. Contact support.
40202Rate limit exceeded.429RequestToo many requests or tasks per minute for this account, or too many access requests from one IP address. The Retry-After header says how many seconds to wait.
40501Invalid field: `<name>`.400 / 200Request / taskA field has a wrong type, format or value; the message names the field, for example "Invalid field: `priority`."
40502Unknown marketplace.200TaskThe marketplace is not one of the 12 supported codes or their aliases.
40503Invalid ASIN.200TaskThe ASIN does not match ^[A-Z0-9]{10}$ after uppercasing.
50000Internal error.500RequestUnexpected server error. The request can be retried; contact support if it persists.