Test Shutterstock licensing and download logic safely using the api-sandbox.shutterstock.com licensing sandbox before going live
domain: api-sandbox.shutterstock.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use the same application credentials, OAuth tokens, and subscription as the production API — the sandbox does not require separate credentials
Point licensing requests at https://api-sandbox.shutterstock.com instead of https://api.shutterstock.com, e.g. POST /v2/images/licenses
Confirm licensing calls return 200 OK with an allotment_charge field, and verify that the charge is not actually deducted from the real subscription
Fetch sandbox-only license history with GET /v2/images/licenses on the sandbox host to confirm the transaction was recorded (retained for at least one week)
Simulate a redownload with POST /v2/images/licenses/{sandbox_license_id}/downloads to verify redownload-permission handling without consuming real quota
Known gotchas
Sandbox image license requests always return the watermarked preview_1500 image (or a preset sample) instead of the real asset — it cannot be used to validate actual delivered file quality
Editorial licensing requests fail unconditionally in the sandbox, so editorial flows must be validated another way
Sandbox license history is isolated from production history and is purged after roughly a week, so it cannot be used as a long-term test record
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?