Before you begin
- Install the Straddle CLI and configure an API key with access to the paykeys you want to inspect.
- Confirm your environment, integration type, and acting account.
- Keep that context and database throughout. For a custom database, add the same
--db PATHto eachsyncandexpiringcommand.
Run the workflow
1
Confirm the account and environment
runtime_context.environment, runtime_context.integration_type, and runtime_context.acting_account. For SaaS or marketplace, select the account if needed and check again:2
Refresh paykeys
sync_complete event and a final sync_summary with success: 1, warned: 0, and errored: 0. Review any sync_warning or sync_anomaly before using the list. Those findings can accompany exit code zero.3
Find expiration and block issues
--days value to use a different planning window.4
Inspect each paykey's current details
PAYKEY_ID with an id from the report. Check the current status, expiration date when present, customer association, and unblocking eligibility before choosing the follow-up.Interpret the results
The result containswindow_days, count, and a paykeys array. Each item’s reason explains why it was included:
Items are ordered by those reasons, then by
days_to_expiry. An expiration reason takes precedence when a paykey also has a recoverable block, so read status and unblock_eligible alongside reason.
expires_at applies to certain paykeys. For an item included because of a block, interpret days_to_expiry only when it has a valid expires_at; a missing date can leave the numeric field at zero. Use the current paykey status to determine usability, including for paykeys outside this report’s expiration and block criteria.