Hi! I love using D&D beyond as a player because it's easy to integrate with my favorite VTTs. Please allow players to continue accessing the .Json files for their characters. Thank you!
I am going to also voice my support for this. You guys JUST got a subscription and every source book purchased by me for this one feature. I was going to start my campaign tonight. I can't imagine buying anything further until this functionality can be returned and my highest tier subscription is now pointless. Thank you for listening.
I'd like to add my voice to this also. I'm a Master Tier subscriber with all of the sourcebooks purchased (I did the Sourcebook Bundle). I was about to purchase the Legendary Bundle this Friday because I also recently discovered Foundry VTT over the last few weeks and have been thoroughly enjoying being able to use my purchased content by importing through VTTAssets. My group's campaign characters all have been imported flawlessly and I was really looking forward to easy imports when they continue to level their characters through my D&D Beyond Campaigns.
Please reconsider allowing the .json endpoint to be utilized again. D&D Beyond is the perfect companion to Foundry VTT by using VTTAssets and I'd love to see that relationship continue to thrive. I've been a Master Tier subscriber for a few years now and this is the first time I've been really excited to be able to finally use my D&D Beyond content with ease.
Please hear our request and bring back the endpoint option!
If you had a VTT that could compete with others, I could see turning this off, but you do not so now I have content and characters trapped in your system that has a dice roller. Congrats on the Random number generation feature. I have over two years of subs and tons of rules bought, but no more. I will cancel now, and when you do finally release the table top I have told everyone I would switch to, I will not, as you do not take into account your customers when making decisions.
I am respectfully adding my voice as a "all-in" DnDBeyond DM and Player. Having an integration point for my players' characters through the json copying to our FoundryVTT was great, and this was why I asked them to keep their character changes and most up-to-date information on DnDBeyond. I would just do a little copy and paste before sessions and I was done. Now, I have a session tomorrow, and have a lot of work to do in a shot time to be ready. I owe it to my players to have a solution as consistent as they are.
Thank you for listening to an otherwise engaged user and Master Tier subscriber to DnDBeyond who owns the Legendary Bundle and considers this my primary resource for an hobby I have had for decades.
I also would like to show my support for the abilty to retrieve formatted character data from ddb. The ability this endpoint allowed in importing characters makes a HUGE difference in my games.
I am a legendary bundle purchaser and buy each new module as it comes out as well as subscribed to the highest tier ddb membership, and this functionality alone would secure me staying that way as it is so monumentally useful.
Please continue to allow the import of character data.
Just a humble Player's manual owner here. I agree that this needs at the least an official response. The silence so far is deafening, especially with the recent moderation activity here.
Another Master-tier subscriber and SourceBook purchaser. I'm a recent convert to FVTT and moved two groups to it in the last month along with putting the players character sheets into DnD Beyond for tracking (which I love for its ease of use, especially for our newer players).
Please continue to offer an API to allow importing character data easily into a VTT. While I like the combat tracker in DnD Beyond, I (and my players) aren't quite ready to go completely theatre-of-the-mind yet. We like having the visuals in terms of the maps and in some cases, the visuals for the spells (cause FVTT does have some plug-ins that make cool visuals). Those are little things, but they do it more fun, and the character importer (and its ease of use) was quite a big bonus upon leveling up.
Getting a refund on all of the $600+ that I spent shortly before DnD Beyond interjecting politics via their social justice pandering makes my decision all the sweeter given that they have essentially removed support for foundry.
Sorry about you guys who can't get your money back. :^)
This is a huge boon for me and makes the D&D Beyond platform my choice. Please find a way for us to get access to our character sheet data. It allows me to easily introduce new players to the game, let them walk through character builder, but not have to then duplicate the work on my end or theirs in whatever VTT I choose to use. Please D&D Beyond staff I'd appreciate if you fix this!
I would just like to further reinforce the sentiments already shared in this thread. The only reason that I started using DnDbeyond is because it makes it easier for me to import resources into my VTT thanks to the great tools of developers like SolFolango. If anything a deep frustration of mine is that more resources aren't accessible via API, but characters at the very least makes it easier for my players to manage their character sheets.
I'd like to show my support on this topic as well. We have been using json output to create characters over at different vtts. So there is a single point of truth and we keep it in sync with data on vtt. I sincerely hope some format stays intact.
Hi. This is going to sound off topic at first, but I promise that it's very germaine. I've been using WotC's official online platforms since the D&D Insider days. I have a top-tier subscription to D&D Beyond, and I have bought many hundreds of dollars' worth of content on this site - almost every item that you have to sell! Almost.
(I bought everything except the Tactical Maps Reincarnated - because, let's be real, what am I gonna use those maps for? It's not like y'all have a VTT I can use them in. We both know that it'd violate the TOS for me to upload them to some other VTT platform. It's not as though I have a large-format printer at home. You released the one pack ages ago, and none since; Y'all already know the maps aren't good for anything... yet.)
... I'm hoping that, if anyone at Fandom or Curse is reading this, that last paragraph made y'all think about how happy I'll be when y'all finally launch the integrated VTT y'all have had in the works on and off for so long. I know y'all have been keeping quiet about recent developments so as not to sour WotC's content licensing relationships with other platforms before Curse is closer to launch. How do I know y'all've been working toward a VTT? I don't exactly need tarot cards and tea leaves to figure out what it means when y'all develop an official, first-party Discord bot, then add a Roll20esque dice roller to the character sheet. There's only once piece of that puzzle missing. C'mon, now.
Here's the thing, though: I've been following the licensed, first-party WotC online content presence since the old days. I remember this 2008 sneak preview video showing how cool the D&D Insider Virtual Table was going to be, back when the VTT space was still ruled by RPTools. RPTools. (smh) I have memories of over a decade of broken promises from WotC and their first-party licensed affiliates about how a slick, cool new VTT was juuuuust around the corner. It has been a "Lucy with the football" situation, and I love Dungeons and Dragons so much that I believed in it against my better judgment, time after time. That mix of hope and faith has led me into giving y'all a BOATLOAD of money. Short of mailing y'all envelopes of cash out of the goodness of my heart, I literally could not be giving Fandom, Inc and WotC any more money for D&D Beyond than I already am. I live in Seattle; if I weren't scared of catching that 'Rona, I'd invite you to coffee just to see if you could look me in the eye and say "on purpose, we broke the rag-tag band of scripts that make our content actually usable for people who can't sit around a physical table to play together, but that's okay because we're going to have a usable replacement ready to go very, very soon."
You don't want people to write bots that scrape whole books' worth of content into other platforms? Fine, I get that. That's reasonable.
Just let me import my dang character sheet into a VTT tool that works. It's a dang character sheet! Don't make me type in all the little numbers by hand. Don't make me copy-paste the little Background paragraph by hand. Just let me import my dang character sheet into a VTT tool that actually, currently, right now, as of this moment, exists and works. Don't make me wait for some rando who somehow codes even more poorly than I do to write some crappy script that scrapes the text off the character sheet pdfs that the character builder tool makes. I know WotC copyright lawyers don't play games. I also know that WotC shot-callers care about the players, most of whom don't run popular streams with sponsorship deals and personal tech support points of contact that will smooth out nonsense like this for them.
Curse, Fandom? Go ask Papa WotC if you can let the dang players have access to the dang jsons for their dang character sheets. C'mon now. You can tell 'em I said "oh, come on, for seven hundred dang-diddly-dollars?"
The only reason I use D&D Beyond is for programmatic access to my characters for import into FoundryVTT via D&D Beyond. The same is true for the 6 players I DM for. Change this and you will lose 7 paying customers. Do you think you could review whether such a decision is commercially sensible?
Foundry VTT user and DnDBeyond master subscriber adding my support to this post. My players and I have come to rely on the easy import capability provided by the API. Please consider leaving it (or an official, published, equivalent) in place.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Hi! I love using D&D beyond as a player because it's easy to integrate with my favorite VTTs. Please allow players to continue accessing the .Json files for their characters. Thank you!
I am going to also voice my support for this. You guys JUST got a subscription and every source book purchased by me for this one feature. I was going to start my campaign tonight. I can't imagine buying anything further until this functionality can be returned and my highest tier subscription is now pointless. Thank you for listening.
I'd like to add my voice to this also. I'm a Master Tier subscriber with all of the sourcebooks purchased (I did the Sourcebook Bundle). I was about to purchase the Legendary Bundle this Friday because I also recently discovered Foundry VTT over the last few weeks and have been thoroughly enjoying being able to use my purchased content by importing through VTTAssets. My group's campaign characters all have been imported flawlessly and I was really looking forward to easy imports when they continue to level their characters through my D&D Beyond Campaigns.
Please reconsider allowing the .json endpoint to be utilized again. D&D Beyond is the perfect companion to Foundry VTT by using VTTAssets and I'd love to see that relationship continue to thrive. I've been a Master Tier subscriber for a few years now and this is the first time I've been really excited to be able to finally use my D&D Beyond content with ease.
Please hear our request and bring back the endpoint option!
If you had a VTT that could compete with others, I could see turning this off, but you do not so now I have content and characters trapped in your system that has a dice roller. Congrats on the Random number generation feature. I have over two years of subs and tons of rules bought, but no more. I will cancel now, and when you do finally release the table top I have told everyone I would switch to, I will not, as you do not take into account your customers when making decisions.
Another voice of support for this access please, from a Master Tier subscriber. Thank you for your consideration.
Master sub and legendary bundle purchaser adding my support to this functionality. It’s integral to my use of dndbeyond.
Hello,
I am respectfully adding my voice as a "all-in" DnDBeyond DM and Player. Having an integration point for my players' characters through the json copying to our FoundryVTT was great, and this was why I asked them to keep their character changes and most up-to-date information on DnDBeyond. I would just do a little copy and paste before sessions and I was done. Now, I have a session tomorrow, and have a lot of work to do in a shot time to be ready. I owe it to my players to have a solution as consistent as they are.
Thank you for listening to an otherwise engaged user and Master Tier subscriber to DnDBeyond who owns the Legendary Bundle and considers this my primary resource for an hobby I have had for decades.
I also would like to show my support for the abilty to retrieve formatted character data from ddb. The ability this endpoint allowed in importing characters makes a HUGE difference in my games.
I am a legendary bundle purchaser and buy each new module as it comes out as well as subscribed to the highest tier ddb membership, and this functionality alone would secure me staying that way as it is so monumentally useful.
Please continue to allow the import of character data.
Just a humble Player's manual owner here. I agree that this needs at the least an official response. The silence so far is deafening, especially with the recent moderation activity here.
Another Master-tier subscriber and SourceBook purchaser. I'm a recent convert to FVTT and moved two groups to it in the last month along with putting the players character sheets into DnD Beyond for tracking (which I love for its ease of use, especially for our newer players).
Please continue to offer an API to allow importing character data easily into a VTT. While I like the combat tracker in DnD Beyond, I (and my players) aren't quite ready to go completely theatre-of-the-mind yet. We like having the visuals in terms of the maps and in some cases, the visuals for the spells (cause FVTT does have some plug-ins that make cool visuals). Those are little things, but they do it more fun, and the character importer (and its ease of use) was quite a big bonus upon leveling up.
adding my voice to this, don't cut off json acces. FVTT new user :)
Getting a refund on all of the $600+ that I spent shortly before DnD Beyond interjecting politics via their social justice pandering makes my decision all the sweeter given that they have essentially removed support for foundry.
Sorry about you guys who can't get your money back. :^)
This is a huge boon for me and makes the D&D Beyond platform my choice. Please find a way for us to get access to our character sheet data. It allows me to easily introduce new players to the game, let them walk through character builder, but not have to then duplicate the work on my end or theirs in whatever VTT I choose to use. Please D&D Beyond staff I'd appreciate if you fix this!
I would just like to further reinforce the sentiments already shared in this thread. The only reason that I started using DnDbeyond is because it makes it easier for me to import resources into my VTT thanks to the great tools of developers like SolFolango. If anything a deep frustration of mine is that more resources aren't accessible via API, but characters at the very least makes it easier for my players to manage their character sheets.
I'd like to show my support on this topic as well. We have been using json output to create characters over at different vtts. So there is a single point of truth and we keep it in sync with data on vtt. I sincerely hope some format stays intact.
I'm also here to voice my support of the feature, It's become one of the main ways my group uses the site.
Hi. This is going to sound off topic at first, but I promise that it's very germaine. I've been using WotC's official online platforms since the D&D Insider days. I have a top-tier subscription to D&D Beyond, and I have bought many hundreds of dollars' worth of content on this site - almost every item that you have to sell! Almost.
(I bought everything except the Tactical Maps Reincarnated - because, let's be real, what am I gonna use those maps for? It's not like y'all have a VTT I can use them in. We both know that it'd violate the TOS for me to upload them to some other VTT platform. It's not as though I have a large-format printer at home. You released the one pack ages ago, and none since; Y'all already know the maps aren't good for anything... yet.)
... I'm hoping that, if anyone at Fandom or Curse is reading this, that last paragraph made y'all think about how happy I'll be when y'all finally launch the integrated VTT y'all have had in the works on and off for so long. I know y'all have been keeping quiet about recent developments so as not to sour WotC's content licensing relationships with other platforms before Curse is closer to launch. How do I know y'all've been working toward a VTT? I don't exactly need tarot cards and tea leaves to figure out what it means when y'all develop an official, first-party Discord bot, then add a Roll20esque dice roller to the character sheet. There's only once piece of that puzzle missing. C'mon, now.
Here's the thing, though: I've been following the licensed, first-party WotC online content presence since the old days. I remember this 2008 sneak preview video showing how cool the D&D Insider Virtual Table was going to be, back when the VTT space was still ruled by RPTools. RPTools. (smh) I have memories of over a decade of broken promises from WotC and their first-party licensed affiliates about how a slick, cool new VTT was juuuuust around the corner. It has been a "Lucy with the football" situation, and I love Dungeons and Dragons so much that I believed in it against my better judgment, time after time. That mix of hope and faith has led me into giving y'all a BOATLOAD of money. Short of mailing y'all envelopes of cash out of the goodness of my heart, I literally could not be giving Fandom, Inc and WotC any more money for D&D Beyond than I already am. I live in Seattle; if I weren't scared of catching that 'Rona, I'd invite you to coffee just to see if you could look me in the eye and say "on purpose, we broke the rag-tag band of scripts that make our content actually usable for people who can't sit around a physical table to play together, but that's okay because we're going to have a usable replacement ready to go very, very soon."
You don't want people to write bots that scrape whole books' worth of content into other platforms? Fine, I get that. That's reasonable.
Just let me import my dang character sheet into a VTT tool that works. It's a dang character sheet! Don't make me type in all the little numbers by hand. Don't make me copy-paste the little Background paragraph by hand. Just let me import my dang character sheet into a VTT tool that actually, currently, right now, as of this moment, exists and works. Don't make me wait for some rando who somehow codes even more poorly than I do to write some crappy script that scrapes the text off the character sheet pdfs that the character builder tool makes. I know WotC copyright lawyers don't play games. I also know that WotC shot-callers care about the players, most of whom don't run popular streams with sponsorship deals and personal tech support points of contact that will smooth out nonsense like this for them.
Curse, Fandom? Go ask Papa WotC if you can let the dang players have access to the dang jsons for their dang character sheets. C'mon now. You can tell 'em I said "oh, come on, for seven hundred dang-diddly-dollars?"
Just want to add another voice to this. Master tier subscriber who is using the module written by SolFolango to keep his players sheets updated.
The only reason I use D&D Beyond is for programmatic access to my characters for import into FoundryVTT via D&D Beyond. The same is true for the 6 players I DM for. Change this and you will lose 7 paying customers. Do you think you could review whether such a decision is commercially sensible?
Foundry VTT user and DnDBeyond master subscriber adding my support to this post. My players and I have come to rely on the easy import capability provided by the API. Please consider leaving it (or an official, published, equivalent) in place.