Skip to main content
Both endpoints below only work before a batch has started processing — once you’ve called Process a bulk transfer, a batch and its items are permanent records. Deleting is for cleaning up mistakes (wrong file uploaded, wrong row, duplicate batchName attempt) before any money moves.
This applies to batches created either way — via Create a bulk transfer (JSON) or Upload via Excel. A freshly created batch is always pending; an uploaded batch may also be enquiry_complete. Both are deletable. Anything past that — processing, completed, failed, partially_completed — is not.

Delete a batch

Permanently deletes the batch and every item in it.

Endpoint

Path parameters

bulkTransferId
string
required
The batch to delete.

Headers

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

Response

status
boolean
true on success.
message
string
"Batch deleted successfully".
data
null
Always null.
This is permanent — there’s no way to recover a deleted batch or its items. bulkReference and every item’s retrievalReference are freed up for reuse afterward, same as if the batch had never been created.

Code examples

Example response

Errors


Delete an item

Removes a single item from a batch — most useful for dropping a row you decided you don’t actually want, as an alternative to editing it.
You can’t delete the last remaining item in a batch — delete the whole batch instead in that case (see above).

Endpoint

Path parameters

bulkTransferId
string
required
The batch the item belongs to.
itemId
string
required
The item to delete.

Headers

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

Response

status
boolean
true on success.
message
string
"Item deleted successfully".
data
null
Always null.
Deleting an item decrements the batch’s totalItems by one, and adjusts completedItems/failedItems to match if the deleted item had already resolved or failed name verification (uploaded batches only — see the field-meaning caveat on Upload via Excel). Any other item’s itemIndex is left as-is; indexes aren’t renumbered.

Code examples

Example response

Errors

See Errors for the full envelope and error code reference.