as requested by the June updates (https://www.dndbeyond.com/changelog/827-character-sheet-changelog-early-june-updates), I am reaching out to you since the /json endpoint seems to be removed. When I read the patchnotes, I instantly tried to get to the JSON data and was very relieved to see that it was still intact. Trying it again today results in a 404.
This is devastating. We are using the data retrieved from that endpoint to get our characters into our games run using Foundry VTT. I am counting ~5000 character imports per day during the last month that were relying to get (somewhat) precise versions of the characters managed on D&D Beyond into our games, it was easy to use and overall an enjoyable experience. Many users voiced their support for D&D Beyond because of such an interaction between the resources provided by you and the easiness of character imports by parsing the JSON.
I would love to get some feedback on how to proceed from here. Enabling at least that endpoint again, or providing a timely alternative would restore the attractiveness of your platform for plenty of people.
Edit: I can see that the /json endpoint of publicly accessible characters is still a thing. Will this endpoint retain or will it get axed, too?
This is really the only reason I am still using this platform. I am dismayed to see you are removing the /json endpoint. I am sure many users will cancel their subscriptions if you don't allow them programmatic access to their own character data.
Looking forward to your feedback and inputs on this matter.
Thanks for this link, krishmero86, the data is almost the same and could be used as future input instead. The big question here is: Which ones will be available throughout the next month, until the eagerly awaited API might be available?
I would just like to add that reliable programmatic access to our own characters is extremely important. In case y'all forgot, a great many of us are nerds.
I would like an official response to this issue if at all possible, as I have been weighing buying the legendary bundle and this has firmly spooked me.
Let´s hope we get some official response to this. We are just switching from Roll20 to Foundry and the easy import was one of the things we really really love.
The only reason I purchased all of the available content on DNDBeyond was so that I would be able to create characters for my players and then we could have programmatic access to those character sheets for use in our VTT games.
I already owned all the hard copies of this same content and I paid for it a whole 2nd time just for this.
Quite disappointed with this execution of the end point prior to the availability of an official public API.
The public API has been on the Trello board for many years, and it's always been one of the things that I have been hoping will come soon, but now it's still sitting on the long term projects - sure it was on the short term at one point.
Surely it would have been better for your customers, to leave the JSON endpoint in place, albeit unsupported, until the API was in place, rather that kill it so suddenly, when there are many users that utilise it for their game, especially under the current covid-19 restrictions still in place in many countries which mean that on-line is their only way of playing.
Quite disappointed with this execution of the end point prior to the availability of an official public API.
You do realise that sounds like saying "I'm quite disappointed you did axe something that was never officially released yet"?
I could understand the disappointment if they suddenly removed a documented and public API without warning, but they have removed something that was never announced as a final endpoint ready for public use...
Rollback Post to RevisionRollBack
--[ Natural 20 - that's how I roll! ]-- We've stopped this OGL madness, but stay vigilant, they tried it once, they can try it again.
I'd like to add my voice to this too. Using Foundry and the json endpoint to let my players build their characters with my bought books and the master tier subscriptions and then importing them for play to foundry. Now I have to rethink our session on saturday :/
Rollback Post to RevisionRollBack
"HUMANS NEED FANTASY TO BE HUMAN. TO BE THE PLACE WHERE THE FALLING ANGEL MEETS THE RISING APE." - DEATH, Hogfather, Sir T. Pratchett
Also want to bump this. I just bought PHB, XGtE, CoS and started a master sub only for the integration into Foundry. If it is lost I doubt I will buy anything ells here and cancel sub.
Quite disappointed with this execution of the end point prior to the availability of an official public API.
You do realise that sounds like saying "I'm quite disappointed you did axe something that was never officially released yet"?
I could understand the disappointment if they suddenly removed a documented and public API without warning, but they have removed something that was never announced as a final endpoint ready for public use...
I am sorry that you cannot understand that having used something for months, and then get it removed because of... reasons with a two-day notice is something to make an expressive post about.
I also use the json to import characters to FoundryVTT and like many others have bought several Source books here because transfering them to the VTT would make it worth to have everyone here build the characters in DND Beyond.
Please consider leaving the json up until you have the API ready.
I'm very disappointed that the fine folks at D&D Beyond thought it was a good idea to take away functionality. I hope beyond hope that they see the error in their ways and come up with a final solution quickly, or revert back what they changed until they can sort it out.
I don't see why people keep talking about reverting the changes and fixing this. Yes, it broke a popular module for a short while, but there is another endpoint to grab the data. I get it is frustrating when a service changes things on short notice. But for now...
A fix is in place. Just update your module.
On a side note, it would be nice to hear from DnDBeyond to confirm that the api we are using now as mentioned above, will not change again in a few months.
I'd just like to add my voice in support of keeping this functionality in some form (ideally making it an official feature and documenting it so that developers can use it more easily if and when it changes).
One more voice to the din here. I'm a subscriber, have purchased all the source material and some dice on D&D Beyond, but use foundry for VTT. Removing this functionality removes my primary use I have for D&D Beyond and would be incredibly disappointing. Here's hoping no further changes occur.
As a Legendary Bundle owner and having recently switched to the amazing Foundry VTT software, this integration has been outstanding and key to my use of the D&D Beyond materials. This is an incredibly useful and powerful integration that only increases the value of the D&D Beyond resources and brand. I strongly suggest enshrining this as part of a formal public API. It would be nice to know that it isn't going to suddenly vanish now that it has proved so useful to so many paying customers.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hi there,
as requested by the June updates (https://www.dndbeyond.com/changelog/827-character-sheet-changelog-early-june-updates), I am reaching out to you since the /json endpoint seems to be removed. When I read the patchnotes, I instantly tried to get to the JSON data and was very relieved to see that it was still intact. Trying it again today results in a 404.
This is devastating. We are using the data retrieved from that endpoint to get our characters into our games run using Foundry VTT. I am counting ~5000 character imports per day during the last month that were relying to get (somewhat) precise versions of the characters managed on D&D Beyond into our games, it was easy to use and overall an enjoyable experience. Many users voiced their support for D&D Beyond because of such an interaction between the resources provided by you and the easiness of character imports by parsing the JSON.
I would love to get some feedback on how to proceed from here. Enabling at least that endpoint again, or providing a timely alternative would restore the attractiveness of your platform for plenty of people.
Edit: I can see that the /json endpoint of publicly accessible characters is still a thing. Will this endpoint retain or will it get axed, too?
Thanks,
Sebastian
Edit: Grammar/ spelling errors.
This is really the only reason I am still using this platform. I am dismayed to see you are removing the /json endpoint. I am sure many users will cancel their subscriptions if you don't allow them programmatic access to their own character data.
Looking forward to your feedback and inputs on this matter.
Thanks,
Ricardo
Looks like access to /json for public characters is also no longer functioning either. That being said,
https://character-service.dndbeyond.com/character/v3/character/number/ is working just change number with the actual number of your character from the URL. Note that it does appear the json data is in a different format.
Hi,
https://character-service.dndbeyond.com/character/v3/character/{characterId} seem to retrieve the character data in json...
--[ Natural 20 - that's how I roll! ]--
We've stopped this OGL madness, but stay vigilant, they tried it once, they can try it again.
Thanks for this link, krishmero86, the data is almost the same and could be used as future input instead. The big question here is: Which ones will be available throughout the next month, until the eagerly awaited API might be available?
Your post was super helpful, thanks again!
I would just like to add that reliable programmatic access to our own characters is extremely important. In case y'all forgot, a great many of us are nerds.
I would like an official response to this issue if at all possible, as I have been weighing buying the legendary bundle and this has firmly spooked me.
Thanks!
Let´s hope we get some official response to this. We are just switching from Roll20 to Foundry and the easy import was one of the things we really really love.
The only reason I purchased all of the available content on DNDBeyond was so that I would be able to create characters for my players and then we could have programmatic access to those character sheets for use in our VTT games.
I already owned all the hard copies of this same content and I paid for it a whole 2nd time just for this.
Quite disappointed with this execution of the end point prior to the availability of an official public API.
Can't help but thinking that this is a bad move.
The public API has been on the Trello board for many years, and it's always been one of the things that I have been hoping will come soon, but now it's still sitting on the long term projects - sure it was on the short term at one point.
Surely it would have been better for your customers, to leave the JSON endpoint in place, albeit unsupported, until the API was in place, rather that kill it so suddenly, when there are many users that utilise it for their game, especially under the current covid-19 restrictions still in place in many countries which mean that on-line is their only way of playing.
You do realise that sounds like saying "I'm quite disappointed you did axe something that was never officially released yet"?
I could understand the disappointment if they suddenly removed a documented and public API without warning, but they have removed something that was never announced as a final endpoint ready for public use...
--[ Natural 20 - that's how I roll! ]--
We've stopped this OGL madness, but stay vigilant, they tried it once, they can try it again.
I'd like to add my voice to this too. Using Foundry and the json endpoint to let my players build their characters with my bought books and the master tier subscriptions and then importing them for play to foundry. Now I have to rethink our session on saturday :/
"HUMANS NEED FANTASY TO BE HUMAN. TO BE THE PLACE WHERE THE FALLING ANGEL MEETS THE RISING APE." - DEATH, Hogfather, Sir T. Pratchett
Also want to bump this. I just bought PHB, XGtE, CoS and started a master sub only for the integration into Foundry. If it is lost I doubt I will buy anything ells here and cancel sub.
I am sorry that you cannot understand that having used something for months, and then get it removed because of... reasons with a two-day notice is something to make an expressive post about.
I also have to add so that our voices are heard.
I also use the json to import characters to FoundryVTT and like many others have bought several Source books here because transfering them to the VTT would make it worth to have everyone here build the characters in DND Beyond.
Please consider leaving the json up until you have the API ready.
I'm very disappointed that the fine folks at D&D Beyond thought it was a good idea to take away functionality. I hope beyond hope that they see the error in their ways and come up with a final solution quickly, or revert back what they changed until they can sort it out.
Bumping. Please, answer our prayers.
I don't see why people keep talking about reverting the changes and fixing this. Yes, it broke a popular module for a short while, but there is another endpoint to grab the data. I get it is frustrating when a service changes things on short notice. But for now...
A fix is in place. Just update your module.
On a side note, it would be nice to hear from DnDBeyond to confirm that the api we are using now as mentioned above, will not change again in a few months.
I'd just like to add my voice in support of keeping this functionality in some form (ideally making it an official feature and documenting it so that developers can use it more easily if and when it changes).
One more voice to the din here. I'm a subscriber, have purchased all the source material and some dice on D&D Beyond, but use foundry for VTT. Removing this functionality removes my primary use I have for D&D Beyond and would be incredibly disappointing. Here's hoping no further changes occur.
As a Legendary Bundle owner and having recently switched to the amazing Foundry VTT software, this integration has been outstanding and key to my use of the D&D Beyond materials. This is an incredibly useful and powerful integration that only increases the value of the D&D Beyond resources and brand. I strongly suggest enshrining this as part of a formal public API. It would be nice to know that it isn't going to suddenly vanish now that it has proved so useful to so many paying customers.