The Miranda API: Difference between revisions
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
One of the real pleasures of working with GraphQL is it is largely self-documenting. Usually when programmers use that phrase, it means they're too busy to describe how their system works. In this, case, however, the kind folks who built GraphQL did a lot of work to support our laziness. The best way to explore a GraphQL API endpoint is using the very cool GraphiQL, (<nowiki>https://github.com/graphql/graphiql</nowiki>) which provides an interface for writing queries, receiving replies, and, best of all, exploring the types of queries the system can answer. | One of the real pleasures of working with GraphQL is it is largely self-documenting. Usually when programmers use that phrase, it means they're too busy to describe how their system works. In this, case, however, the kind folks who built GraphQL did a lot of work to support our laziness. The best way to explore a GraphQL API endpoint is using the very cool GraphiQL, (<nowiki>https://github.com/graphql/graphiql</nowiki>) which provides an interface for writing queries, receiving replies, and, best of all, exploring the types of queries the system can answer. | ||
Read our API guide written by the technical team at ParsonsTKO. Please note: This version was written in accompaniment to our Miranda beta launch, and represents work done so far. It is not final documentation. | [[:File:Miranda API Introduction (1).pdf|Read our API guide]] written by the technical team at ParsonsTKO. Please note: This version was written in accompaniment to our Miranda beta launch, and represents work done so far. It is not final documentation. | ||
Revision as of 16:08, 9 January 2019
Miranda has a fabulous web interface available at collections.folger.edu/, but that's not all. Our interface relies upon a GraphQL API available to all comers at https://collections.folger.edu/graphql.
An API, or Application Programming Interface, is a way for programs to talk to each other. (Or, sometimes, for dedicated individuals to talk to computer programs.) GraphQL offers an approach to APIs that lets the requestor define what is returned.
One of the real pleasures of working with GraphQL is it is largely self-documenting. Usually when programmers use that phrase, it means they're too busy to describe how their system works. In this, case, however, the kind folks who built GraphQL did a lot of work to support our laziness. The best way to explore a GraphQL API endpoint is using the very cool GraphiQL, (https://github.com/graphql/graphiql) which provides an interface for writing queries, receiving replies, and, best of all, exploring the types of queries the system can answer.
Read our API guide written by the technical team at ParsonsTKO. Please note: This version was written in accompaniment to our Miranda beta launch, and represents work done so far. It is not final documentation.