- Apr 2023
-
linked.art linked.art
Tags
Annotators
URL
-
- Mar 2023
-
dummyjson.com dummyjson.com
-
- Feb 2023
- Jan 2023
-
reconciliation-api.github.io reconciliation-api.github.io
Tags
Annotators
URL
-
- Aug 2022
-
stackoverflow.com stackoverflow.com
-
The vendor prefix (vnd.) indicates that it is custom for this vendor.
-
The +json indicates that it can be parsed as JSON, but the media type should define further semantics on top of JSON.
-
- Jun 2022
-
chelseatroy.com chelseatroy.com
-
The creator of GraphQL admits this. During his presentation on the library at a Facebook internal conference, an audience member asked him about the difference between GraphQL and SOAP. His response: SOAP requires XML. GraphQL defaults to JSON—though you can use XML.
-
Conclusion There are decades of history and a broad cast of characters behind the web requests you know and love—as well as the ones that you might have never heard of. Information first traveled across the internet in 1969, followed by a lot of research in the ’70s, then private networks in the ’80s, then public networks in the ’90s. We got CORBA in 1991, followed by SOAP in 1999, followed by REST around 2003. GraphQL reimagined SOAP, but with JSON, around 2015. This all sounds like a history class fact sheet, but it’s valuable context for building our own web apps.
-
- May 2022
-
medium.com medium.com
-
json { "success": true, "message": "User logged in successfully", "data": { "user": { "id": 2, "name": "Client", "client_id": 1, "email": "client@clickapps.co", "gender_label": null, "gender": null, "mobile": "123654789", "code_country": "00967", "birth_date": null, "avatar": "http://localhost:3000/default_image.png", "sms_notification": true, "is_mobile_verified": false, "otp": { "otp": "8704" }, "client_city": { "id": 3, "name_ar": "الرياض", "name_en": "Riadh", "name": "Riadh", "status": 1, "status_label": "Active", "country": { "id": 2, "name": "Kingdub saudi Arab", "code_country": "ksa", "avatar": "http://localhost:3000/default_image.png", "status": 1, "status_label": "Active" } }, "client_locations": [ { "id": 1, "client_id": 1, "latitude": "0.0", "longitude": "0.0", "address": "169 Rath Rapids", "address_ar": "964 Michale Parkway", "address_en": "169 Rath Rapids", "building_name": "building_name", "location_type": 1, "location_type_label": "Home", "apartment_name": null, "require_permission": false, "city": null, "zip_code": null } ] }, "role": "client", "token": "eyJhbGciOiJIUzI1NiJ9.eyJpZCI6MiwibmFtZSI6IkNsaWVudCIsImVtYWlsIjoiY2xpZW50QGNsaWNrYXBwcy5jbyIsIm1vYmlsZSI6IjEyMzY1NDc4OSIsImltYWdlIjoiL2RlZmF1bHRfaW1hZ2UucG5nIiwiYWRtaW4iOmZhbHNlLCJpYXQiOjE1NDc5MjU0MzIsImV4cCI6MTU1MDUxNzQzMn0.4Vyjd7BG7v8AFSmGKmIs4VM2FBw3gOLn97Qdf6U4jxU" } }
-
-
jsonapi.org jsonapi.org
-
-
www.hydra-cg.com www.hydra-cg.com
-
``` HTTP/1.1 200 OK Content-Type: application/ld+json Link: http://api.example.com/doc/; rel="http://www.w3.org/ns/hydra/core#apiDocumentation"
{ "@context": "http://www.w3.org/ns/hydra/context.jsonld", "@graph": [{ "@id": "http://api.example.com/people", "@type": "hydra:Collection", "api:personByName": "api:PersonByNameTemplate" }, { "@id": "http://api.example.com/events", "@type": "hydra:Collection", "api:eventByName": "api:EventByNameTemplate" } } ```
Tags
Annotators
URL
-
- Apr 2022
-
info.orcid.org info.orcid.org
Tags
Annotators
URL
-
- Mar 2022
-
road.issn.org road.issn.org
- Jan 2022
-
pro.europeana.eu pro.europeana.eu
-
The Annotations API is an extension to the Europeana REST API which allows you to create, retrieve and manage annotations on Europeana objects. Annotations are user-contributed or system-generated enhancements, additions or corrections to (or a selection of) metadata or media. We adopted the Web Annotation Data Model as a base model for the representation of annotations and as a format for exchanging annotations between client applications and the API, but also the Web Annotation Protocol as base HTTP protocol for the API.
Example:
{ "@context": “http://www.w3.org/ns/anno.jsonld” "id": "http://data.europeana.eu/annotations/1", "type": "Annotation", "created": "2015-03-10T14:08:07Z", "creator": { "type": "Person", "name": "John Smith" }, "generated": "2015-04-01T09:00:00Z", "generator": { "type": "Software", "name": "HistoryPin", "homepage": "https://www.historypin.org/" }, "motivation": "tagging", "bodyValue": "MyBeautifulTag", "target": "http://data.europeana.eu/item/92062/BibliographicResource_1000126189360" }
Tags
Annotators
URL
-
-
linked.art linked.artAPI1
Tags
Annotators
URL
-
- Feb 2021
-
-
What do you do with your API key? "WHERE DO I PUT IT?!?" https://youtu.be/ecT42O6I_WI?t=338
Also, suggests to get a JSON formatter browser extension. e.g.: "JSON Formatter" from the Chrome Web Store Here's a good one: https://chrome.google.com/webstore/detail/json-viewer/gbmdgpbipfallnflgajpaliibnhdgobh/
Tags
Annotators
URL
-
-
www.youtube.com www.youtube.com
-
API endpoint filters are given as % encoded JSON: https://youtu.be/VT-chUoq-oo?t=221
Fields reference for endpoint:files: https://api.gdc.cancer.gov/files/_mapping
Fields reference for endpoint:genes: https://api.gdc.cancer.gov/genes/_mapping
Tags
Annotators
URL
-
-
apidocs.getresponse.com apidocs.getresponse.com
Tags
Annotators
URL
-
- Nov 2020
-
stackoverflow.com stackoverflow.com
-
I have created a thin wrapper around fetch() with many improvements if you are using a purely json REST API:
-
- Sep 2018
-
jsonplaceholder.typicode.com jsonplaceholder.typicode.com
Tags
Annotators
URL
-
- Apr 2017
-
jsonapi.org jsonapi.org
-
JSON API requires use of the JSON API media type (application/vnd.api+json) for exchanging data.
means to change the
Acceptfield andContent-Typefield
-