Thank you dndbeyond for a really friendly and supportive answer to the api question. I am really glad to see though undocumented but open api! Love you devs
And thank you Sebastian for vtta, this tool really saves me about 1-2 hours each time I prepare for the session.
So I do hope they can start devoting resources towards a true public API soon, but for the few who are venting anger about this, it is misplaced.
They have never said they would support it, and were actually quite clear in stating repeatedly for almost 3 years now that it was not a public API and it was subject to change or removal. So, in the spirit of whatever that saying is about catching flies and sugar or whatever, let's encourage them to devote the resources to a true public API rather than yelling at them about removing something they have said for over 3 years they might remove at any time. :) Because not just creating but continually supporting a public API right is a massive job and would take resources away from other feature development. So a case needs to be made beyond venting anger.
So I do hope they can start devoting resources towards a true public API soon, but for the few who are venting anger about this, it is misplaced.
They have never said they would support it, and were actually quite clear in stating repeatedly for almost 3 years now that it was not a public API and it was subject to change or removal. So, in the spirit of whatever that saying is about catching flies and sugar or whatever, let's encourage them to devote the resources to a true public API rather than yelling at them about removing something they have said for over 3 years they might remove at any time. :) Because not just creating but continually supporting a public API right is a massive job and would take resources away from other feature development. So a case needs to be made beyond venting anger.
I have seen very civil remarks about the current usage and the desire to have such an endpoint, and while the expression of that desire was definitely express vocally, I do not recall any of them "angered" or think that D&D Beyond was being "yelled" at. It speaks for this platform that some people - including you - are here to say that they publicly expressed those endpoints being unofficial, but does that invalidate this thread? In the EOL announcement, it was specificially requested that we should showcase what we are/have been using the endpoints, so I guess it's not. But let's not go into that direction, in the end everyone wants two things: A great platform with great tools.
I do believe that we all agree that a well-crafted, well-documented and supported API is a great addition to an otherwise already great toolset provided by D&D Beyond. And yes, this is quite an undertaking, and I do appreciate their willingness to devote developer time into it.
Just here to throw my support behind an official API at some point. It's the flexibility of being able to manage my content in one location and have flexibility in using that content in a VTT, whether that's Foundry today (my current choice), or another in the future, that keeps me wanting to spend my money here at D&D Beyond, versus with a provider that locks you into their ecosystem.
I'm just getting back into D&D after almost a decade off, so online resources and VTT's for D&D I'm relatively new to, but wanted the flexibility which is why I settled on D&D Beyond and Foundry VTT to get back into the game with.
My hat's off to all the folks at D&D Beyond, Foundry VTT and VTT Assets for making it all possible!
So I do hope they can start devoting resources towards a true public API soon, but for the few who are venting anger about this, it is misplaced.
They have never said they would support it, and were actually quite clear in stating repeatedly for almost 3 years now that it was not a public API and it was subject to change or removal. So, in the spirit of whatever that saying is about catching flies and sugar or whatever, let's encourage them to devote the resources to a true public API rather than yelling at them about removing something they have said for over 3 years they might remove at any time. :) Because not just creating but continually supporting a public API right is a massive job and would take resources away from other feature development. So a case needs to be made beyond venting anger.
While it's true that people probably shouldn't be hostile about the removal of an API that was always an undocumented feature, for some people they've probably only very recently spent hundreds of dollars on content (likely due to the on-going pandemic) that relies on that functionality working for it to be useful to them. They are probably not developers and have no idea what an API is, probably haven't been using DnDBeyond for three years and ultimately all they are aware of is that the hundreds of dollars they just spent may no longer usable for their needs. If I was in their shoes I would probably feel quite angry.
That said, I think most people in this thread have been reasonably cordial given it was a potentially upsetting change and if we didn't voice our opinions on this then the team at DnDBeyond wouldn't be aware of how important this is to so many dm's and players.
My apologies if I implied everyone or the idea behind this thread was being unreasonable. The majority definitely are being quite reasonable, and I don't want to distract. Just reading some who were more indignant and treating this as some sort of betrayal, when DDB has been saying not to rely on this because it would go away. But having DDB now looking into the actual uses of this for a future public API is an excellent step forward! :)
I just like to add in here, first a Thank you to Molster and BadEyeAdam for addressing this and while I understand this was never supported it was still frustrating to have it taken down in the manner which it was. That said I appreciate you committing to not block us from utilizing the endpoints you set up for your use and I think communicating that its there, but is not supported, at least to some of the lead 'community developers' such as SolFolango/VTTA would go a long way in supporting us.
And I say this because, and I apologize for being a bit critical here, but DNDBeyond/Curse' development cycles are painfully slow. We're now nearly 3 years in and we still dont have a functional mobile app that can support a character sheet (yes I know the mobile web version works) and we're just now getting 3d rollable dice, a feature which Fantasy Grounds and Roll20 have had for... nearly decade? It took 2 years for an Encounter Builder to come to fruition, and another 6 months to integrate the Combat Tracker that *must* have been being worked on in tandem. Ive personally been following threads and asking about an API for over 2 years now. I work for AWS and if our dev cycles were as slow as D&D Beyond's have been we'd have been crushed out of the marketplace long ago. Im not really interested in waiting another 5-8 years for an official API to be released. We can work with unofficial and while I understand some of the frustration the community has expressed, at the same time it has always been unsupported. That said, it shouldn't matter. Being flexible and agile in development gets things done rapidly but... has chances like this where something breaks and we have to scramble to adapt to the change. We dont work/develop inside of D&D Beyond/Curse/Fandom so we cant set up things like Version Sets where we can ingest a portion of the code we need for our item to run so it can remain stable as we adapt to the change. This is the nature of ad hoc developing, so while I can understand some frustration, anyone getting the nasties needs to chill because we cant be upset at Curse/DnDBeyond for taking away something they never reallygave us to begin with. Especially since we DEFINITELY dont want them slowing down on our account.
What we do is say, thank you for continuing to allow us access to the stuff you're using, we appreciate as much advance notice of endpoint decommission as is possible for you to give us, we WILL carry on and, while we do indeed look forward to the future official updates, features and services you are working to provide us with... we might just beat you across that finish line.
That said... this 3d dice marketplace. I'll give you every bit of the mythic pack, those are friggin cool, but $15? And come on, $7.96 for the pigment pack which essentially boils down to the alteration of the RGB values? Man at least give me a slider or color picker so I can match the hue I want, and give me the option to change the color of the numbering. What is this, League of Legends?
I've had Legendary Bundle for Two years, but stopped purchasing the adventures some time ago as I had not found a VTT that made it worth while. With Foundry VVT, and Sebastians' integration work I've been very excited about topping off the Legendary Bundle with the rest of the content.
If you had a formal API that was accessible to approved developers to allow more such integrations it will drive more content sales and utilization. This is a strong enhancement and complement to what you provide, and a along with the Player App which I've been looking forward to since the release of the Compendium App this integration has made me very excited to use these tools with in my games.
Thank you for your time and consideration in reviewing these comments, I look forward to everyone's improved success!
This news sucks, but it's understandable. I guess we'll all have to put in the extra work to bring characters into our VTTs. I'm using Roll20 for my games and was using the JSON Importer script to bring character sheets in, that was super convenient. If anyone comes up with a way to import using these links https://character-service.dndbeyond.com/character/v3/character/{characterId} let us know, cause it doesn't work with the !beyond --import script.
Thanks for responding, Molster. DnD Beyond is great, and its integration with third party apps and VTT's like Foundry is why I'm using it. An official API that permits third-party apps would be amazing.
I agree with the sentiment of other users. Consider my voice more wood to the fire.
Thank you Molster and the D&D Beyond staff for responding to this post, and for updating your subscribers.
I'm going to add my voice to the chorus here on creating a robust API for DDB! Hopefully you heard the news today that FVTT has partnered with World Anvil and now has a module for integrating world building with Foundry. Having DDB as a vital partner with these two amazing products strengthens all of you!
Being able to create in World Anvil, then populate from DDB, and then play in FVTT is a potential future I never thought I'd see. One that is exciting and full of tremendous possibilities! Can you just imagine R.A. Salvatore, Erin M Evans or Ed Greenwood (to name but a few current authors) at the helm of such a Possibility Engine!
This news sucks, but it's understandable. I guess we'll all have to put in the extra work to bring characters into our VTTs. I'm using Roll20 for my games and was using the JSON Importer script to bring character sheets in, that was super convenient. If anyone comes up with a way to import using these links https://character-service.dndbeyond.com/character/v3/character/{characterId} let us know, cause it doesn't work with the !beyond --import script.
I've forked the old importer project and started updating it again. The new version works with the the new links.
Yeah I'd also like to direct my stifled cries of nerd rage into the void here. I I run a weekly PvP game on foundry vtt, players join my DDBeyond campaign, create a character using my purchased books and then I import those characters into foundry. It's super easy and is the main reason I purchased all the DDBeyond source books. If that's not possible then either I spend ages manually importing all the class features and races and such or I just give up and cry. It will likely be the second one.
In general I just want all the data as final result like the final Armor Class from the character sheet in a simple JSON but without all the extra book content.
The main feedback at this stage we are looking for, would be from various app developers, and knowing what they would be looking for in a fully supported API.
I am also curious where to send API feedback. The more I work on coding for the roll20 character importer, the more my head hurts dealing with how this data is structured. It's just...extremely inconsistent in how it handles things--Metamagic, for example is handled and presented differently than almost every other 'choice-based' class mechanic. Artificer infusions are even worse.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Great news!
Very glad that this is being worked out. Thanks DND Beyond!
I love the rattle of dice and a good story.
Thank you dndbeyond for a really friendly and supportive answer to the api question. I am really glad to see though undocumented but open api! Love you devs
And thank you Sebastian for vtta, this tool really saves me about 1-2 hours each time I prepare for the session.
FYI: I know it's a great feature but since day 1 (literally, the very day I first posted about finding the JSON endpoint back on Sept 12, 2017) they have been extremely clear and consistent that it was not for public use and would change or be removed.
So I do hope they can start devoting resources towards a true public API soon, but for the few who are venting anger about this, it is misplaced.
They have never said they would support it, and were actually quite clear in stating repeatedly for almost 3 years now that it was not a public API and it was subject to change or removal. So, in the spirit of whatever that saying is about catching flies and sugar or whatever, let's encourage them to devote the resources to a true public API rather than yelling at them about removing something they have said for over 3 years they might remove at any time. :) Because not just creating but continually supporting a public API right is a massive job and would take resources away from other feature development. So a case needs to be made beyond venting anger.
I have seen very civil remarks about the current usage and the desire to have such an endpoint, and while the expression of that desire was definitely express vocally, I do not recall any of them "angered" or think that D&D Beyond was being "yelled" at. It speaks for this platform that some people - including you - are here to say that they publicly expressed those endpoints being unofficial, but does that invalidate this thread? In the EOL announcement, it was specificially requested that we should showcase what we are/have been using the endpoints, so I guess it's not. But let's not go into that direction, in the end everyone wants two things: A great platform with great tools.
I do believe that we all agree that a well-crafted, well-documented and supported API is a great addition to an otherwise already great toolset provided by D&D Beyond. And yes, this is quite an undertaking, and I do appreciate their willingness to devote developer time into it.
Just here to throw my support behind an official API at some point. It's the flexibility of being able to manage my content in one location and have flexibility in using that content in a VTT, whether that's Foundry today (my current choice), or another in the future, that keeps me wanting to spend my money here at D&D Beyond, versus with a provider that locks you into their ecosystem.
I'm just getting back into D&D after almost a decade off, so online resources and VTT's for D&D I'm relatively new to, but wanted the flexibility which is why I settled on D&D Beyond and Foundry VTT to get back into the game with.
My hat's off to all the folks at D&D Beyond, Foundry VTT and VTT Assets for making it all possible!
I'm here to throw in my support for allowing us to import data into 3rd party VTT and associated tools.
@Molster Great news, and thank you and D&D Beyond for 1) listening, and 2) making happen to keep PC API available at new location.
Well played!-)
Thank you to the DnDBeyond team for the positive response.
While it's true that people probably shouldn't be hostile about the removal of an API that was always an undocumented feature, for some people they've probably only very recently spent hundreds of dollars on content (likely due to the on-going pandemic) that relies on that functionality working for it to be useful to them. They are probably not developers and have no idea what an API is, probably haven't been using DnDBeyond for three years and ultimately all they are aware of is that the hundreds of dollars they just spent may no longer usable for their needs. If I was in their shoes I would probably feel quite angry.
That said, I think most people in this thread have been reasonably cordial given it was a potentially upsetting change and if we didn't voice our opinions on this then the team at DnDBeyond wouldn't be aware of how important this is to so many dm's and players.
Further Edit: Official API soon please :(
My apologies if I implied everyone or the idea behind this thread was being unreasonable. The majority definitely are being quite reasonable, and I don't want to distract. Just reading some who were more indignant and treating this as some sort of betrayal, when DDB has been saying not to rely on this because it would go away. But having DDB now looking into the actual uses of this for a future public API is an excellent step forward! :)
I just like to add in here, first a Thank you to Molster and BadEyeAdam for addressing this and while I understand this was never supported it was still frustrating to have it taken down in the manner which it was. That said I appreciate you committing to not block us from utilizing the endpoints you set up for your use and I think communicating that its there, but is not supported, at least to some of the lead 'community developers' such as SolFolango/VTTA would go a long way in supporting us.
And I say this because, and I apologize for being a bit critical here, but DNDBeyond/Curse' development cycles are painfully slow. We're now nearly 3 years in and we still dont have a functional mobile app that can support a character sheet (yes I know the mobile web version works) and we're just now getting 3d rollable dice, a feature which Fantasy Grounds and Roll20 have had for... nearly decade? It took 2 years for an Encounter Builder to come to fruition, and another 6 months to integrate the Combat Tracker that *must* have been being worked on in tandem. Ive personally been following threads and asking about an API for over 2 years now. I work for AWS and if our dev cycles were as slow as D&D Beyond's have been we'd have been crushed out of the marketplace long ago. Im not really interested in waiting another 5-8 years for an official API to be released. We can work with unofficial and while I understand some of the frustration the community has expressed, at the same time it has always been unsupported. That said, it shouldn't matter. Being flexible and agile in development gets things done rapidly but... has chances like this where something breaks and we have to scramble to adapt to the change. We dont work/develop inside of D&D Beyond/Curse/Fandom so we cant set up things like Version Sets where we can ingest a portion of the code we need for our item to run so it can remain stable as we adapt to the change. This is the nature of ad hoc developing, so while I can understand some frustration, anyone getting the nasties needs to chill because we cant be upset at Curse/DnDBeyond for taking away something they never really gave us to begin with. Especially since we DEFINITELY dont want them slowing down on our account.
What we do is say, thank you for continuing to allow us access to the stuff you're using, we appreciate as much advance notice of endpoint decommission as is possible for you to give us, we WILL carry on and, while we do indeed look forward to the future official updates, features and services you are working to provide us with... we might just beat you across that finish line.
That said... this 3d dice marketplace. I'll give you every bit of the mythic pack, those are friggin cool, but $15? And come on, $7.96 for the pigment pack which essentially boils down to the alteration of the RGB values? Man at least give me a slider or color picker so I can match the hue I want, and give me the option to change the color of the numbering. What is this, League of Legends?
Hello,
I've had Legendary Bundle for Two years, but stopped purchasing the adventures some time ago as I had not found a VTT that made it worth while. With Foundry VVT, and Sebastians' integration work I've been very excited about topping off the Legendary Bundle with the rest of the content.
If you had a formal API that was accessible to approved developers to allow more such integrations it will drive more content sales and utilization. This is a strong enhancement and complement to what you provide, and a along with the Player App which I've been looking forward to since the release of the Compendium App this integration has made me very excited to use these tools with in my games.
Thank you for your time and consideration in reviewing these comments, I look forward to everyone's improved success!
I would also like to add my voice to those who wish an official API - espcially linked to Foundry VTT.
Never underestimate the Importance of Session 0!
This news sucks, but it's understandable. I guess we'll all have to put in the extra work to bring characters into our VTTs. I'm using Roll20 for my games and was using the JSON Importer script to bring character sheets in, that was super convenient. If anyone comes up with a way to import using these links https://character-service.dndbeyond.com/character/v3/character/{characterId} let us know, cause it doesn't work with the !beyond --import script.
Thanks for responding, Molster. DnD Beyond is great, and its integration with third party apps and VTT's like Foundry is why I'm using it. An official API that permits third-party apps would be amazing.
I agree with the sentiment of other users. Consider my voice more wood to the fire.
Thank you Molster and the D&D Beyond staff for responding to this post, and for updating your subscribers.
I'm going to add my voice to the chorus here on creating a robust API for DDB! Hopefully you heard the news today that FVTT has partnered with World Anvil and now has a module for integrating world building with Foundry. Having DDB as a vital partner with these two amazing products strengthens all of you!
Being able to create in World Anvil, then populate from DDB, and then play in FVTT is a potential future I never thought I'd see. One that is exciting and full of tremendous possibilities! Can you just imagine R.A. Salvatore, Erin M Evans or Ed Greenwood (to name but a few current authors) at the helm of such a Possibility Engine!
I've forked the old importer project and started updating it again. The new version works with the the new links.
https://github.com/kjbro/Roll20APIScripts/tree/master/BeyondImporter_5eOGL
Yeah I'd also like to direct my stifled cries of nerd rage into the void here. I I run a weekly PvP game on foundry vtt, players join my DDBeyond campaign, create a character using my purchased books and then I import those characters into foundry. It's super easy and is the main reason I purchased all the DDBeyond source books. If that's not possible then either I spend ages manually importing all the class features and races and such or I just give up and cry. It will likely be the second one.
Where do we provide feedback on API.
In general I just want all the data as final result like the final Armor Class from the character sheet in a simple JSON but without all the extra book content.
I am also curious where to send API feedback. The more I work on coding for the roll20 character importer, the more my head hurts dealing with how this data is structured. It's just...extremely inconsistent in how it handles things--Metamagic, for example is handled and presented differently than almost every other 'choice-based' class mechanic. Artificer infusions are even worse.