An API doesn't have to expose the whole database, just the endpoints that the database holder wants to. Additionally, it's possible to use authentication, such as OAuth for example, to validate API requests against a users account to check permissions and limit request rate. So there are checks and balances that can be put in place to avoid API abuse and database scraping.
As for going 'open source', APIs rarely (if ever) expose source code such as what DDB uses for the toolset, they're used for making database queries.
If/when DDB releases a public facing API, they'll be able to manage user access permissions and rights accordingly to ensure that it doesn't harm their service. That's the purpose of API, controlled channels of access to allow external services to make safe calls.
An API doesn't have to expose the whole database, just the endpoints that the database holder wants to. Additionally, it's possible to use authentication, such as OAuth for example, to validate API requests against a users account to check permissions and limit request rate. So there are checks and balances that can be put in place to avoid API abuse and database scraping.
As for going 'open source', APIs rarely (if ever) expose source code such as what DDB uses for the toolset, they're used for making database queries.
If/when DDB releases a public facing API, they'll be able to manage user access permissions and rights accordingly to ensure that it doesn't harm their service. That's the purpose of API, controlled channels of access to allow external services to make safe calls.
doesn't matter, is what i'm saying ! look at twitch, look at google. look at facebook. in the end, those who uses the API, do not even use the interface at all. so continue to explain to me, why DDB would want people to use their database and not their interface when the primary thing they sell is their interface ?
and don't get me wrong, if they ever allow us to use the database, i'll be the first one to use it for my own monster maker and combat tracker. but i really doubt they'll ever accept that.
DM of two gaming groups. Likes to create stuff. Check out my homebrew --> Monsters --> Magical Items --> Races --> Subclasses If you like --> Upvote, If you wanna comment --> Comment
Play by Post Games --> One Shot Adventure - House of Artwood (DM) (Completed)
An API doesn't have to expose the whole database, just the endpoints that the database holder wants to. Additionally, it's possible to use authentication, such as OAuth for example, to validate API requests against a users account to check permissions and limit request rate. So there are checks and balances that can be put in place to avoid API abuse and database scraping.
As for going 'open source', APIs rarely (if ever) expose source code such as what DDB uses for the toolset, they're used for making database queries.
If/when DDB releases a public facing API, they'll be able to manage user access permissions and rights accordingly to ensure that it doesn't harm their service. That's the purpose of API, controlled channels of access to allow external services to make safe calls.
doesn't matter, is what i'm saying ! look at twitch, look at google. look at facebook. in the end, those who uses the API, do not even use the interface at all. so continue to explain to me, why DDB would want people to use their database and not their interface when the primary thing they sell is their interface ?
Hey, DDB put it on the roadmap buddy, not us. You don’t like it go take it to the feedback forum.
An API doesn't have to expose the whole database, just the endpoints that the database holder wants to. Additionally, it's possible to use authentication, such as OAuth for example, to validate API requests against a users account to check permissions and limit request rate. So there are checks and balances that can be put in place to avoid API abuse and database scraping.
As for going 'open source', APIs rarely (if ever) expose source code such as what DDB uses for the toolset, they're used for making database queries.
If/when DDB releases a public facing API, they'll be able to manage user access permissions and rights accordingly to ensure that it doesn't harm their service. That's the purpose of API, controlled channels of access to allow external services to make safe calls.
doesn't matter, is what i'm saying ! look at twitch, look at google. look at facebook. in the end, those who uses the API, do not even use the interface at all. so continue to explain to me, why DDB would want people to use their database and not their interface when the primary thing they sell is their interface ?
Hey, DDB put it on the roadmap buddy, not us. You don’t like it go take it to the feedback forum.
they put it there because people requested it. but is it number one or even in the top 10 ? so it is up to you guys to make it go up, not me, because i'm not wanting this.
Rollback Post to RevisionRollBack
DM of two gaming groups. Likes to create stuff. Check out my homebrew --> Monsters --> Magical Items --> Races --> Subclasses If you like --> Upvote, If you wanna comment --> Comment
Play by Post Games --> One Shot Adventure - House of Artwood (DM) (Completed)
An API doesn't have to expose the whole database, just the endpoints that the database holder wants to. Additionally, it's possible to use authentication, such as OAuth for example, to validate API requests against a users account to check permissions and limit request rate. So there are checks and balances that can be put in place to avoid API abuse and database scraping.
As for going 'open source', APIs rarely (if ever) expose source code such as what DDB uses for the toolset, they're used for making database queries.
If/when DDB releases a public facing API, they'll be able to manage user access permissions and rights accordingly to ensure that it doesn't harm their service. That's the purpose of API, controlled channels of access to allow external services to make safe calls.
doesn't matter, is what i'm saying ! look at twitch, look at google. look at facebook. in the end, those who uses the API, do not even use the interface at all. so continue to explain to me, why DDB would want people to use their database and not their interface when the primary thing they sell is their interface ?
Hey, DDB put it on the roadmap buddy, not us. You don’t like it go take it to the feedback forum.
they put it there because people requested it. but is it number one or even in the top 10 ? so it is up to you guys to make it go up, not me, because i'm not wanting this.
I don’t give a shit either way, I’m just boarded of the non-constructive complaining.
so continue to explain to me, why DDB would want people to use their database and not their interface when the primary thing they sell is their interface ?
and don't get me wrong, if they ever allow us to use the database, i'll be the first one to use it for my own monster maker and combat tracker. but i really doubt they'll ever accept that.
Presumably they'd restrict access to content you have purchased, so they'd still be selling stuff even if you're using it elsewhere. Presumably they could also link API access to a subscription. I'm sure people could circumvent that, but that's what lawyers are for.
the reality being that one would need access to the profile as well to know what is and what is not accessible. nothing could stop anybody from creating an API that actually query the database and copy it to say a file on his disk, and then just recreate the database per say. thats exactly what people have done with lions'den database and look what people are doing by today's standard. nobody uses the lions den software they all create their own based on the database that was created by them.
an API might seem restricted, but imagine a guy who, like me already bought everything, and now has access tot heir database. why would i create anything that would add to their interface when i could just create my own softwares and just use that database. here lies my question. why would you use their interface if you have access to their database and started creating your own ?
If you want to be more precise onto what i hope they will do though. is the ability to add to Beyond interface. like addons that the site could allow. much like google chrome does right now with beyond helper, which brings much needed functionnality to the interface. clicking on the map numbers to get a preview of the number or to go directly to the number is just awesome. this is something DDB doesn't do at all. yet this addons does it. dice rollers, its not pretty but beyond helper, the google chrome addons has been doing this for like a year now. folders for characters and campaign notes ! that addons does it already. that i am ok with, they add features to the interface. the API you seem to be requesting is literally just a way to use their database. so i'm wondering, at that point why not just allow DDB the use of addons created for DDB instead ? addons like the google chrome beyond helper already do things i want ddb to do. and i think that guy is on the right track. he didn't need the database at all at that point either.
Rollback Post to RevisionRollBack
DM of two gaming groups. Likes to create stuff. Check out my homebrew --> Monsters --> Magical Items --> Races --> Subclasses If you like --> Upvote, If you wanna comment --> Comment
Play by Post Games --> One Shot Adventure - House of Artwood (DM) (Completed)
The reason they'd want an API would be so folks could integrate with their VTT and campaign management instead of moving to a different company which provides both a VTT and a Campaign manager. This should seem obvious. I love DnDbeyond. But often use a competing product because I can't integrate my maptool and personal forum with the campaign character sheets and encounters. Unless DnDbeyond offers an API then the benefits don't match what is already on the market. Much less exceed them.
Ha, more like it is sitting on the way back burner as the style refit was way more important than a VTT. Of Course before that they said no to having one, so who knows.
Ha, more like it is sitting on the way back burner as the style refit was way more important than a VTT. Of Course before that they said no to having one, so who knows.
No, they have different teams all over the world working on different projects. Look at the situation: for the past 9 months they have been re-redoing the character sheet to get all the information pulling correctly, that is part and parcel with the same system revamp that will allow for both the Class Feature Variants and the homebrew revamp. You can tell they must be ramping up because the number of “Bug” and “Request” flags in that forum jumped and then tons of them got “resolved,” most likely at least in part because of that work. They are working on the Encounter Builder, the Combat Tracker, and the Digital Dice. You know what you get when you put all of that together? The framework for a VTT that will be way more 5e compatible than anything you have ever seen before.
An API doesn't have to expose the whole database, just the endpoints that the database holder wants to. Additionally, it's possible to use authentication, such as OAuth for example, to validate API requests against a users account to check permissions and limit request rate. So there are checks and balances that can be put in place to avoid API abuse and database scraping.
As for going 'open source', APIs rarely (if ever) expose source code such as what DDB uses for the toolset, they're used for making database queries.
If/when DDB releases a public facing API, they'll be able to manage user access permissions and rights accordingly to ensure that it doesn't harm their service. That's the purpose of API, controlled channels of access to allow external services to make safe calls.
Find my D&D Beyond articles here
doesn't matter, is what i'm saying !
look at twitch, look at google. look at facebook.
in the end, those who uses the API, do not even use the interface at all.
so continue to explain to me, why DDB would want people to use their database and not their interface when the primary thing they sell is their interface ?
and don't get me wrong, if they ever allow us to use the database, i'll be the first one to use it for my own monster maker and combat tracker.
but i really doubt they'll ever accept that.
DM of two gaming groups.
Likes to create stuff.
Check out my homebrew --> Monsters --> Magical Items --> Races --> Subclasses
If you like --> Upvote, If you wanna comment --> Comment
Play by Post Games
--> One Shot Adventure - House of Artwood (DM) (Completed)
Hey, DDB put it on the roadmap buddy, not us. You don’t like it go take it to the feedback forum.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
they put it there because people requested it.
but is it number one or even in the top 10 ?
so it is up to you guys to make it go up, not me, because i'm not wanting this.
DM of two gaming groups.
Likes to create stuff.
Check out my homebrew --> Monsters --> Magical Items --> Races --> Subclasses
If you like --> Upvote, If you wanna comment --> Comment
Play by Post Games
--> One Shot Adventure - House of Artwood (DM) (Completed)
I don’t give a shit either way, I’m just boarded of the non-constructive complaining.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
My apologies everyone. This would have never happened if I hadn’t asked what an API is. Sorry.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
You are not responsible for other's shitposts.
Check out all my important links here.
May we live in Less Interesting Times
I’m Catholic, we feel guilty for everything. We’re the only people on earth actually born guilty.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I'm a Polish-heritage Jew. We make others feel guilty. ;P
Check out all my important links here.
May we live in Less Interesting Times
Presumably they'd restrict access to content you have purchased, so they'd still be selling stuff even if you're using it elsewhere. Presumably they could also link API access to a subscription. I'm sure people could circumvent that, but that's what lawyers are for.
the reality being that one would need access to the profile as well to know what is and what is not accessible.
nothing could stop anybody from creating an API that actually query the database and copy it to say a file on his disk, and then just recreate the database per say. thats exactly what people have done with lions'den database and look what people are doing by today's standard. nobody uses the lions den software they all create their own based on the database that was created by them.
an API might seem restricted, but imagine a guy who, like me already bought everything, and now has access tot heir database. why would i create anything that would add to their interface when i could just create my own softwares and just use that database. here lies my question. why would you use their interface if you have access to their database and started creating your own ?
If you want to be more precise onto what i hope they will do though. is the ability to add to Beyond interface. like addons that the site could allow. much like google chrome does right now with beyond helper, which brings much needed functionnality to the interface. clicking on the map numbers to get a preview of the number or to go directly to the number is just awesome. this is something DDB doesn't do at all. yet this addons does it. dice rollers, its not pretty but beyond helper, the google chrome addons has been doing this for like a year now. folders for characters and campaign notes ! that addons does it already. that i am ok with, they add features to the interface. the API you seem to be requesting is literally just a way to use their database. so i'm wondering, at that point why not just allow DDB the use of addons created for DDB instead ? addons like the google chrome beyond helper already do things i want ddb to do. and i think that guy is on the right track. he didn't need the database at all at that point either.
DM of two gaming groups.
Likes to create stuff.
Check out my homebrew --> Monsters --> Magical Items --> Races --> Subclasses
If you like --> Upvote, If you wanna comment --> Comment
Play by Post Games
--> One Shot Adventure - House of Artwood (DM) (Completed)
The reason they'd want an API would be so folks could integrate with their VTT and campaign management instead of moving to a different company which provides both a VTT and a Campaign manager. This should seem obvious. I love DnDbeyond. But often use a competing product because I can't integrate my maptool and personal forum with the campaign character sheets and encounters. Unless DnDbeyond offers an API then the benefits don't match what is already on the market. Much less exceed them.
Wouldn't this issue go away if dndbeyond builds their own VTT? i mean, just give us a place to use maps we buy, and content we buy right here. :)
They’re working on it.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
sorry, pretty new to the forums, is there a link you can show me so i can track the progress?
i remember early on i found a graph that showed yellow/green/red projects/tasks but i cannot find that roadmap stuff anymore.
Unrelated: the "Completed " block on trello still lists items from last year.
https://trello.com/b/vIKxuEs8/dd-beyond-feature-roadmap
Trying to Decide if DDB is for you? A few helpful threads: A Buyer's Guide to DDB; What I/We Bought and Why; How some DMs use DDB; A Newer Thread on Using DDB to Play
Helpful threads on other topics: Homebrew FAQ by IamSposta; Accessing Content by ConalTheGreat;
Check your entitlements here. | Support Ticket LInk
So... items that have been completed already?
Ha, more like it is sitting on the way back burner as the style refit was way more important than a VTT. Of Course before that they said no to having one, so who knows.
I just want to tell everyone "happy gaming" and actually mean it. Whatever your game is, just have fun with it, it is after all, just a game.
No, they have different teams all over the world working on different projects. Look at the situation: for the past 9 months they have been re-redoing the character sheet to get all the information pulling correctly, that is part and parcel with the same system revamp that will allow for both the Class Feature Variants and the homebrew revamp. You can tell they must be ramping up because the number of “Bug” and “Request” flags in that forum jumped and then tons of them got “resolved,” most likely at least in part because of that work. They are working on the Encounter Builder, the Combat Tracker, and the Digital Dice. You know what you get when you put all of that together? The framework for a VTT that will be way more 5e compatible than anything you have ever seen before.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting