Skip to main content
Bulk endpoints exist for volume, and because deletion is bulk-only they are also how you delete a single link.

Creating

Each object takes the same fields as create_shortlink, except the image upload.

Deleting

Including a single link — there is no other way to delete one:
bulk_edit covers disable and enable as well:
action is delete, disable or enable. Disabling is reversible and keeps analytics; deleting is neither.

Reading the result

A bulk call returns 200 even when individual items failed. The request succeeded; some items did not.
status grades the whole call: success, partial_success, or error. Each item carries outcome, which is success, error or skipped.
summary.succeeded + summary.failed + summary.skipped always equals the length of results. If you only check the HTTP status, a batch where every item failed looks identical to one where every item worked.

All-or-nothing

By default a batch processes every item and reports what happened. Pass stop_on_error=true to abort and roll back at the first failure instead:
Use it when a partially-applied batch would be worse than none of it — for example when links are being created in a fixed set that has to be complete.

Processing more than 100

Chunk, and pace yourself against the rate limit:
continue after a 429 re-sends the same batch. Advancing past it on a rate-limit response silently drops those links, which is the kind of bug you find weeks later.

Before a large create

Check your plan allowance first, so you fail before doing half the work:
Running out mid-batch surfaces as FEATURE_LIMIT_EXCEEDED on the remaining items.