All integrations
Gift Up!
BUSINESS · COMMERCE & FINANCE
Issue, redeem, and top up gift cards on that account’s own store.
Connecting Gift Up! in practice
Throughput is a leaky bucket at 5 requests a second per key, burstable to 10 for roughly five minutes, and the only thing separating a test order from a real one is a single request header: x-giftup-testmode: true. Forget it and Gift Up charges its fee on the order you just created.
Rate limits
- Leaky bucket: 5 requests per second sustained per API key, burst up to 10 per second for about 5 minutes.
- Responses slow down as volume rises before Gift Up returns HTTP 429 for severe violations.
- List endpoints page with limit (default 10, maximum 100) and offset (default 0), returning total and hasMore.
Worth knowing
- Test mode is a header, not a separate key or base URL, so the same credential against https://api.giftup.app can create either test data or billable live orders depending on one header an agent may drop on retry.
- The documentation is explicit that developing against live mode means "you will be charged our fee if you create any new orders" — there is no free live sandbox.
- The default page size of 10 makes a naive list-everything loop ten times more requests than the 100 maximum would, and 5 requests a second is a low budget to spend that way.
- Plain HTTP calls fail outright rather than redirecting, so a misconfigured base URL looks like a connectivity problem.
Checked against Gift Up! API (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Gift Up! behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.