SentryKit

Sync Amazon listing alerts from SentryKit into your destination for reporting on Buy Box changes, inventory and listing health.

Set up a source

1. In SentryKit, open Settings → API Keys and create a read-only API key.
2. Select SentryKit in Daspire and enter the key in API Key.
3. Optionally set Start date to an ISO-8601 timestamp with a timezone, such as 2026-08-01T00:00:00Z. The default is 30 days before the first sync.
4. Test the connection and select the alerts stream.
5. Choose Incremental + Append deduped when your destination supports date-time cursors, using id as the primary key. An hourly schedule is a suggested starting point; adjust it to your account's API allowance and reporting needs.

Data and incremental behavior

Field	Description
id	SentryKit's original Alert ID; destination primary key.
created_at	UTC event time, converted from the provider's millisecond timestamp.
alert_type	Alert type reported by SentryKit.
seller_account_id, asin	Optional seller and product identifiers.
marketplace_id	Null when the API does not provide a marketplace ID.
payload	The complete original alert, including type-specific and newly added fields.

Full refresh reads available alerts from the configured start date. Incremental sync reads a fixed time window and includes a 24-hour overlap for late events. The source splits this window into consecutive ranges of at most 24 hours. Progress advances only after all pages in a range finish. After an interruption, completed ranges stay committed and the unfinished range restarts at its first page, keeping the original end time. Use destination deduplication or a downstream merge by id to absorb replay and the overlap; plain append retains duplicates.

Historical availability depends on the SentryKit account. The default start date does not extend the provider's retention. The source reads Alerts only; it does not change listings or configure webhooks.

Troubleshooting

• Authentication failed: replace the API key and check its read permission.
• Rate limited: wait for the provider's retry deadline or reduce frequency.
• Read incomplete: retry from the saved state. A read exceeding 1,000 pages fails explicitly and does not report incomplete data as successfully synced.
• Unexpected response or duplicate pagination: retain the saved state and contact support. Errors omit credentials and original alert contents.

Credentials belong in the secure source form. Never put the API key in a URL, state document or MCP message.

Destination compatibility

The created_at cursor is a UTC date-time string. A destination's deduplication mode must support that cursor type. The current Clean MySQL destination accepts only integer deduplication cursors, so its Append deduped mode cannot be used with this source. Use a compatible destination, or Append with a downstream merge keyed by id. Plain append retains repeated alerts from the overlap window.