Bungie.Net API

Name: Bungie.Net API
Brand: Bungie.Net API
Availability: InStock

✓ Official Vendor SpecMediaContent DeliveryapiKey, oauth2160 EndpointsREST

For Agents

Read Destiny 2 player profiles, inventories, and stats and perform in-game actions like equipping items, transferring loadouts, and managing clans on behalf of an authenticated player.

Install Jentic One Beta

Connect the Bungie.Net API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bungie.Net API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbungie.net%2Fbungie" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbungie.net%2Fbungie" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Bungie.Net API.

Look up a player's Destiny 2 profile, characters, inventory, and progressions

Equip, transfer, lock, or pull from postmaster on Destiny 2 items

Snapshot, equip, and update Destiny 2 loadouts

GET STARTED

Start building with Bungie.Net API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Bungie.Net API for, with concrete tasks.

★ Destiny 2 companion app data

Power third-party companion apps that show a player's vault, characters, weapons, and progressions. The Destiny2 endpoints return profile components, character inventories, and item instances with manifest IDs that map to the public definition catalog. Apps typically combine this with the Destiny manifest to render rich item details client-side.

For a given Destiny 2 membershipId and membershipType, fetch the player's profile components and list their characters and equipped items.

In-game item actions on behalf of a player

Perform OAuth-scoped item actions like equipping a weapon, transferring an item between vault and character, locking a god-roll, or snapshotting a loadout. These are write operations that require the MoveEquipDestinyItems scope and a valid user OAuth token. They power loadout managers and DIM-style inventory tools.

POST to /Destiny2/Actions/Items/EquipItem/ with the itemInstanceId and characterId for a player who has authorized the MoveEquipDestinyItems scope, then verify by re-reading the character's equipped items.

Clan and fireteam management

Build clan dashboards and LFG tools using the GroupV2 and FireteamFinder endpoints. Read clan membership, post to clan walls with the appropriate scope, and create or browse open fireteam listings filtered by activity. Suitable for clan websites, Discord bots, and matchmaking utilities.

List open Fireteam Finder listings for a given activity graph hash and return the top results with their joinability and language.

AI agent Destiny assistant via Jentic

An AI assistant can read a player's current Destiny 2 state and execute scoped item actions on their behalf - for example, suggesting and equipping a loadout for a specific activity. Jentic stores the OAuth refresh token and the X-API-Key separately, so the agent only ever calls operations with scoped, short-lived credentials.

Search Jentic for 'equip a Destiny 2 loadout', load the EquipLoadout schema, then execute it with the player's characterId and chosen loadoutIndex after confirming the player intent.

Key Endpoints

160 endpoints — the bungie.

METHOD

PATH

DESCRIPTION

POST

/Destiny2/Actions/Items/EquipItem/

Equip an item on a character

POST

/Destiny2/Actions/Items/TransferItem/

Transfer an item between vault and character

POST

/Destiny2/Actions/Items/PullFromPostmaster/

Pull an item from the postmaster

POST

/Destiny2/Actions/Loadouts/EquipLoadout/

Equip a saved loadout

POST

/Destiny2/Actions/Loadouts/SnapshotLoadout/

Snapshot the current equipped state as a loadout

GET

/Destiny2/Armory/Search/{type}/{searchTerm}/

Search Destiny entity definitions

GET

/Content/Rss/NewsArticles/{pageToken}/

Fetch the Bungie.net news article feed

POST

/Destiny2/Actions/Items/EquipItem/

Equip an item on a character

POST

/Destiny2/Actions/Items/TransferItem/

Transfer an item between vault and character

POST

/Destiny2/Actions/Items/PullFromPostmaster/

Pull an item from the postmaster

POST

/Destiny2/Actions/Loadouts/EquipLoadout/

Equip a saved loadout

POST

/Destiny2/Actions/Loadouts/SnapshotLoadout/

Snapshot the current equipped state as a loadout

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Bungie.Net API by hand means learning its X-API-Key header alongside a per-user OAuth authorization-code flow against www.bungie.net/Platform and refreshing tokens yourself. Through Jentic you install once, import the Bungie.Net API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Bungie's Destiny 2 actions target the character and items through the request body rather than the URL path, so scope the agent by the operations it needs, such as equipping a loadout or searching the armory. Because you choose the allowed operations, it can equip and snapshot loadouts without being able to transfer items or pull from the postmaster unless you add those.

Credential isolation

Your Bungie X-API-Key and per-user OAuth refresh token are stored once, encrypted, by your own Jentic One instance, and only a scoped short-lived access token is injected at execution time. The long-lived secrets never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'equip a Destiny 2 loadout' or 'search the armory', and Jentic returns the matching Destiny2 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Bungie.Net API through Jentic.

What authentication does the Bungie.Net API use?

Every request requires an X-API-Key header obtained from https://www.bungie.net/en/Application. Operations that read or modify a user's data additionally require OAuth 2.0 authorization-code with scopes such as ReadDestinyInventoryAndVault or MoveEquipDestinyItems. Through Jentic, both the API key and the user OAuth refresh token are vault-scoped per call.

Can I equip a loadout on behalf of a Destiny 2 player?

Yes - POST /Destiny2/Actions/Loadouts/EquipLoadout/ swaps to a saved loadout. The request requires a valid OAuth token with the MoveEquipDestinyItems scope. Use SnapshotLoadout to capture the current state before swapping if you want a rollback.

How do I search for a Destiny 2 item by name?

GET /Destiny2/Armory/Search/{type}/{searchTerm}/ returns Destiny entity definitions matching the search term. Resolve the returned hashes against the Destiny manifest to get full item, perk, or activity details.

What are the rate limits for the Bungie.Net API?

The OpenAPI spec does not declare explicit limits. Bungie publishes throttle guidance in their developer documentation - most endpoints are subject to per-application and per-user quotas. Cache profile data where possible and avoid polling tighter than the platform's recommended cadence.

How do I read a player's Destiny 2 profile through Jentic?

Run `pip install jentic` and search for 'get a Destiny 2 player profile'. Jentic returns the matching GetProfile operation under Destiny2 with its component query parameter; load the schema and execute with the player's membershipType and membershipId - credentials stay in your Jentic One instance.

Can I post to Bungie.net forums and clan walls with this API?

Yes. The Forum and GroupV2 endpoints support creating posts and replies. Posting to a clan wall requires the WriteGroups OAuth scope, and forum write operations require the BnetWrite scope, which Bungie restricts to elevated-trust applications.

Can I limit what my agent is allowed to do with the Bungie.Net API?

Yes. Because Jentic One is self-hosted and you decide which operations your agent may call, you can grant it just the Destiny 2 actions it needs, such as equipping and snapshotting loadouts or searching the armory. Bungie's item actions target the character and items through the request body rather than the URL path, so an agent scoped to EquipLoadout and SnapshotLoadout cannot transfer items or pull from the postmaster unless you explicitly add those operations. Your X-API-Key and per-user OAuth refresh token stay in your own instance, and only a scoped short-lived access token is injected when a permitted call runs.

Bungie.Net API

Connect the Bungie.Net API to your agent

Capabilities

Start building with Bungie.Net API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs