read

Recent entries from the decision log, each carrying the bucket the Decisions page files it under: live (applied) / queue

Recent entries from the decision log, each carrying the bucket the Decisions page files it under: live (applied) / queued / failed / suggested / reverted / noop (no change). READ THE BUCKET BEFORE DESCRIBING A ROW. Most stores are dominated by "no change" bookkeeping — one carries 2,178 of 2,217 — so a list of recent rows is not a list of changes, and calling one a change is wrong by two orders of magnitude. Use mode to ask for one bucket: "suggested" is what a merchant can still act on, "queued" is what runs next. The whole-store counts per bucket are in get_store_overview.decisions — this call returns at most limit rows and is never a denominator.

post/api/v1/tools/get_recent_decisions

Request

  • Base URL: https://app.magistry.io
  • URL: https://app.magistry.io/api/v1/tools/get_recent_decisions
  • Auth: one of:
    • HTTP bearer
    • OAuth 2 (authorization code, authorization URL https://app.magistry.io/api/oauth/authorize, token URL https://app.magistry.io/api/oauth/token, scopes: automation:read)

Request body

mode'all' | 'live' | 'queued' | 'suggested' | 'reverted' | 'failed' | 'expired' | 'noop'

Which bucket to return: live (applied), queued, failed, suggested, reverted, noop (no change), or all (default).

window_daysinteger

How many days back to look (default 7, max 30). Counts are whole-store.

to_statestring

Optional: filter to a target lifecycle state (e.g. "DRAFT", "WINNER").

appliedboolean

Optional: true = only rows that reached Shopify; false = only rows that did not. Prefer mode — a row that never reached Shopify is not necessarily a proposal.

handlestring

Optional: one product handle.

limitinteger

Max decisions to return (default 10, max 50).

Response

Tool result

okboolean required
resultunknown required

Changes

No recorded changes to this operation across all 3 revisions of this API.