Skip to content
Other

bungie.net

Bungie.Net sandbox and mock API

These endpoints constitute the functionality exposed by Bungie.net, both for more traditional website functionality and for connectivity to Bungie video games and their related functionality. Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
134
Collections
-
Event types
-
Start this simulation
example request
curl https://your-bungie.slurry.io/Platform/App/FirstParty/ \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 2.18.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 134.

  • GET/App/ApiUsage/{applicationId}/
  • GET/App/FirstParty/
  • GET/CommunityContent/Get/{sort}/{mediaFilter}/{page}/
  • GET/Content/GetContentById/{id}/{locale}/
  • GET/Content/GetContentByTagAndType/{tag}/{type}/{locale}/
  • GET/Content/GetContentType/{type}/
  • GET/Content/Rss/NewsArticles/{pageToken}/
  • GET/Content/Search/{locale}/
  • GET/Content/SearchContentByTagAndType/{tag}/{type}/{locale}/
  • GET/Content/SearchHelpArticles/{searchtext}/{size}/
  • POST/Destiny2/Actions/Items/EquipItem/
  • POST/Destiny2/Actions/Items/EquipItems/