Connect Bungie.Net and Polygon
Describe what you want to happen between Bungie.Net and Polygon in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Bungie.Net
134 documented operations. See all Bungie.Net operations
- POSTGiven the prefix of a global display name
/User/Search/GlobalName/{page}/ - POSTAdd a new optional conversation/chat channel
/GroupV2/{groupId}/OptionalConversations/Add/ - POSTEquip an item. You must have a valid Destiny Account
/Destiny2/Actions/Items/EquipItem/ - POSTEquip a list of items by itemInstanceIds
/Destiny2/Actions/Items/EquipItems/ - POSTSearch for Groups
/GroupV2/Search/ - POSTSet the Lock State for an instanced item
/Destiny2/Actions/Items/SetLockState/
Polygon
10 documented operations. See all Polygon operations
- GETAvailable Companies
/v1/companies - GETAvailable Currencies
/v1/currencies - GETLast Trade for a Symbol
/v1/last/stocks/{symbol} - GETLast Quote for a Symbol
/v1/last_quote/stocks/{symbol} - GETLast Trade for a Currency Pair
/v1/last/currencies/{from}/{to} - GETHistoric Quotes
/v1/historic/quotes/{symbol}/{date}
How a Bungie.Net and Polygon automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Bungie.Net and Polygon, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Bungie.Net and OData for namespace microsoft.graph11,546 operations
- OData for namespace microsoft.graph and Polygon11,422 operations
- Bungie.Net and Cloudflare3,256 operations
- Cloudflare and Polygon3,132 operations
- Bungie.Net and NetBox978 operations
- NetBox and Polygon854 operations
- Bungie.Net and GitHub945 operations
- GitHub and Polygon821 operations
- Bungie.Net and Mist902 operations
- Mist and Polygon778 operations
Questions about connecting Bungie.Net and Polygon
- Can Bungie.Net connect with Polygon?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Bungie.Net to Polygon?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Bungie.Net and Polygon?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Bungie.Net and Polygon?
- Bungie.Net publishes 134 documented operations and Polygon publishes 10. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Bungie.Net or Polygon is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Bungie.Net and Polygon. Descriptions are each provider’s own words, not ours.