Logs for a batch
Returns reprocess log entries for every item in a batch, most recent first.Endpoint
Path parameters
The batch to fetch reprocess logs for.
Headers
Your public API key.
Your API secret. Use a
stl_test_... value in sandbox, stl_live_... in production.Your business ID.
Query parameters
Page number. Defaults to
1.Records per page. Defaults to
20, capped at 100.Filter to logs whose outcome was this status. One of
completed, failed, pending.Filter to logs triggered by this actor type. One of
member, admin, system.ISO 8601 date — only include logs created on or after this date.
ISO 8601 date — only include logs created on or before this date.
Response
true on success.Human-readable outcome.
Reprocess log entries, most recently created first.
Unique ID for this log entry.
The batch this log entry belongs to.
The item this log entry is about.
The transaction reference the item had immediately before this reprocess attempt.
The new transaction reference generated for this attempt.
ID of whoever (or whatever) triggered this reprocess — a member ID or your API client’s ID, depending on
triggeredByType.Who triggered this attempt:
member (dashboard user), api (an API-key request like this one), admin, or system.Display name of the trigger, if available.
null for API-triggered attempts.The item’s status immediately before this attempt — always
failed, since only failed items are eligible for reprocessing.The item’s resulting status after this attempt.
null while the attempt is still in flight.Why the attempt failed, if
newStatus is failed. null otherwise.ISO 8601 timestamp of when this reprocess attempt was initiated.
The current page number.
The page size used for this response.
Total number of log entries matching the current query, across all pages.
The final page number, derived from
total ÷ limit.Code examples
Example response
Errors
| Status | Cause |
|---|---|
400 Bad Request | bulkTransferId isn’t a valid UUID, or a filter value fails validation (e.g. an out-of-range limit, or an invalid new_status/triggered_by_type) |
401 Unauthorized | businessId header missing, or credentials invalid |
404 Not Found | No bulk transfer with this ID exists for your client and business |
Logs for a single item
Same as above, scoped to one item within a batch.Endpoint
Path parameters
The batch the item belongs to.
The item to fetch reprocess logs for.
Headers
Your public API key.
Your API secret. Use a
stl_test_... value in sandbox, stl_live_... in production.Your business ID.
Query parameters
Page number. Defaults to
1.Records per page. Defaults to
20, capped at 100.Filter to logs whose outcome was this status. One of
completed, failed, pending.ISO 8601 date — only include logs created on or after this date.
ISO 8601 date — only include logs created on or before this date.
Unlike the batch-level endpoint above, this one does not support filtering by
triggered_by_type.Response
Same response shape as logs for a batch above, filtered to the one item.Code examples
Errors
| Status | Cause |
|---|---|
400 Bad Request | bulkTransferId or itemId isn’t a valid UUID, or a filter value fails validation |
401 Unauthorized | businessId header missing, or credentials invalid |
404 Not Found | No bulk transfer with this ID exists for your client and business, or no item with this ID exists in that batch |