Skip to main content
Interstellas gives you two ways to retry failed transfers: reprocess an entire batch’s failed items at once, or reprocess a specific set of one or more items yourself. Both are asynchronous — they return 202 Accepted immediately and do the actual work in the background. Poll Get a bulk transfer to see the outcome, or query reprocess logs for a full audit trail of every attempt.
Only items in failed status can be reprocessed. completed items are left untouched by both endpoints below.

Reprocess failed items in a batch

Retries every failed item in a batch. Items that are completed are skipped; the request has no effect on them.

Endpoint

Path parameters

string
required
The ID of the batch to reprocess.

Headers

string
required
Your public API key.
string
required
Your API secret. Use a stl_test_... value in sandbox, stl_live_... in production.
string
required
Your business ID.

Response

boolean
true on success.
string
"Bulk transfer reprocessing started" if any items were queued, or "No failed items to reprocess" if the batch has none.
string
The batch that was reprocessed.
integer
Number of failed items that were queued for retry. 0 if there was nothing to reprocess.
Before starting, Interstellas checks that your business account has enough available balance to cover the sum of all failed items being retried. If it doesn’t, the request fails outright (see Errors below) rather than partially retrying — this differs from a normal batch, where an insufficient-funds failure is per-item, discovered during processing.

Code examples

Example response

Errors


Reprocess items

Retries one or more specific items you choose, without touching any other item in the batch. Use this instead of the batch-level endpoint above when you only want to retry a subset of what failed.

Endpoint

Path parameters

string
required
The ID of the batch the items belong to.

Headers

string
required
Your public API key.
string
required
Your API secret. Use a stl_test_... value in sandbox, stl_live_... in production.
string
required
Your business ID.

Request body

array
required
A non-empty array of item ids to reprocess, from the items array in Get a bulk transfer. Every ID must belong to this batch.

Response

boolean
true on success.
string
"Transfer item reprocessing started" when itemIds has exactly one entry, or "{n} transfer items reprocessing started" for more than one.
string
The batch the items belong to.
integer
The number of items queued for retry — equal to the length of itemIds you sent.
A 202 here means the item IDs were valid and belong to this batch — it does not mean every item was actually eligible to retry. Each item is still individually required to be in failed status; an item that isn’t (e.g. already completed, or picked up by a concurrent reprocess request) is silently skipped in the background rather than causing the whole request to fail. itemsQueued reflects what you asked for, not what actually got retried. Poll Get a bulk transfer or check item reprocess logs to confirm which items actually changed state.
Unlike the previous single-item version of this endpoint, the response no longer includes a newTransactionReference — since items are now processed as a background batch rather than synchronously set up one at a time, the new reference for each item is only visible via Get a bulk transfer (items[].transactionReference) or the item’s reprocess logs once processing completes.

Code examples

Example response

Errors

Unlike the request-level errors above, per-item eligibility problems (item not failed, or a concurrent reprocess already claimed it) don’t surface as an HTTP error at all — see the Warning under Response. See Errors for the full envelope and error code reference.