Search the Community

Showing results for tags 'api'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • Brandon and Book News
  • Events, Signings, & Giveaways
  • Columns and Features
  • Site News
  • Shardcast

Forums

  • 17th Shard
    • Introduce Yourself!
    • 17th Shard Discussion
    • The Coppermind Wiki
    • Arcanum Discussion
  • Brandon Sanderson
    • General Brandon Discussion
    • Events and Signings
    • Sanderson Fan Works
    • Arcanum, the Brandon Sanderson Archive
  • Spoiler Zone
    • The Lost Metal (Mistborn Spoilers Only)
    • The Lost Metal (Cosmere Spoilers)
  • The Cosmere
    • Cosmere Q&A
    • Cosmere Discussion
    • Cosmere Secret Projects
    • Stormlight Archive
    • Mistborn
    • Elantris and Emperor's Soul
    • Warbreaker
    • White Sand
    • Cosmere Short Stories
    • Unpublished Works
  • Non-cosmere Works
    • Non-cosmere Secret Project
    • The Reckoners
    • Skyward
    • The Rithmatist
    • Alcatraz
    • Dark One
    • Other Stories
    • The Wheel of Time
  • Related Works
    • Writing Excuses
    • Reading Excuses
    • TWG Archive
  • Community
    • General Discussion
    • Entertainment Discussion
    • Science, Tech, and Math Discussion
    • Creator's Corner
    • Role-Playing
    • Social Groups, Clans, and Guilds

Blogs

  • Chaos' Blog
  • Leinton's Blog
  • 17th Shard Blog
  • KChan's Blog
  • Puck's Blag
  • Brandon's Blog
  • Darth Squirrely's Blog
  • Tales of a Firebug
  • borborygmus' Blog
  • Zeadman's Blog
  • zas678's Blog
  • The Basement
  • Addy's Avocations
  • Zarepath's Blog
  • First time reading The Well Of Ascension
  • Seshperankh's Blog
  • "I Have Opinions About Books"
  • Test
  • Which actors would you like to see playing the characters of Mistborn?
  • Drifted Mists
  • Jaron's Realm
  • Roshar Speculative Theories
  • ChrisHamatake's Blog
  • Paradox Flint's Blog
  • Deoradhan's Blog
  • Storm Blessed's Blog
  • Elwynn's Blog
  • firstRainbowRose's Blog
  • Rotabush ShardBlog
  • Hoid's Compendium
  • InterContinental Adventures
  • Claincy Creates
  • WoR Thoughts and Questions
  • Blogfalcon
  • David Coppercloud's Blog
  • yurisses' notes and theories
  • Lark Adventures
  • LUNA's Poetry
  • Inspiration Board
  • Trying to be Useful for a Change
  • The Way of Toasters
  • Cosmere Nerd Things
  • Dapper's Music Blog
  • Shhh Spoilers for Ronald.
  • Wyn's Adventures in Geekiness
  • Words With Ene
  • Dapper's Blog
  • Things to talk about, stuff to do
  • Zelly's Healthy-Accountability Blog
  • Even These Acronyms
  • Rhythm of War Liveblog
  • Unnecessarily Overcomplicated
  • Star's Art Blog
  • Weather Reports
  • Axioms Idioms & Adages
  • The Blog of Dubious Copyright Legality
  • Trutharchivist's Rambles
  • 5
  • Xino's corner of insanity
  • The Perfect Space Opera
  • My Journey Through Roshar (A Liveblog)

Calendars

  • Community Calendar

Found 1 result

  1. Hello, all! One topic of conversation on the Discord as-of-late has been an eventual API for the Arcanum library. I've made this thread in hopes of helping our amazing dev team with ideas as to what form this should take. If you can think of any uses for this API, please comment them below so they can know what features are wanted. I'd start off by recommending that the API returns a JSON array to users since that's the easiest method I know of to allow integration with things like bots. For human users, it wouldn't be the best, but people can just use the search anyways. This JSON array would be filled with all relevant WoBs, each of which would be an object containing information such as the date, the event, the speaker(s) (as an array), the tags, the footnotes, and of course the main content. I've seen this strategy used well before in another API whose link I can provide at request The other question is what format the API requests should be made in. I think that each request should be able to fill any number of available fields, which would include those options on the search menu (text, earliest date, latest date, speaker, tags, antitags, and ordering style), as well as those options which can be achieved with special characters such as ampersands for "and" or exclamation marks for "not". While I'm not sure these fields would all be used too often, they'd be better to integrate from the start, and shouldn't be too difficult given they're already worked into queries. I could, of course, be wrong about it being difficult - it's notoriously challenging to predict how resistant to change a system you've never seen before is. I've started "hard" projects and been done in an hour, but sometimes what "should be easy" has taken many hundreds of times as long Finally, a very low priority request that I nonetheless think would be great is giving each user an API key. That API key could be used to query results that have been "favorited" by that keyholder for easy reference. I'm not sure how this would be implemented, but it would likely require modifications to the SQL. Another potential future option would be to let people query WoBs they've gotten with this key, where each user could query the speaker as an API key and be returned all WoBs which the keyholder marked as originating from them. This could further be possibly integrated with existing "speaker" data, where each user could say who they are and have their WoBs automatically synced to their key. This would be a lot of work for a little gain, however, so I'd consider this a very low priority feature