Using the READ API, you can Read the Schema Docs.

Root
https://api.jsonbin.io/
Route
/s/<SCHEMA_ID>
Request Type
GET
Request Headers
Header Value Required
secret-key <YOUR_SECRET_KEY> Yes
secret-key

secret-key is always required to create a Schema Doc.

Basic Code Samples
curl --header "Content-Type: application/json" \
     --header "secret-key: <YOUR_SECRET_KEY>" \
     --request GET \
        https://api.jsonbin.io/s
                    
let req = new XMLHttpRequest();

req.onreadystatechange = () => {
  if (req.readyState == XMLHttpRequest.DONE) {
    console.log(req.responseText);
  }
};

req.open("PUT", "https://api.jsonbin.io/s", true);
req.setRequestHeader("secret-key", "<YOUR_SECRET_KEY>");
req.send();
import requests
url = 'https://api.jsonbin.io/s'
headers = {'secret-key': '<YOUR_SECRET_KEY>'}
data = ''
req = requests.get(url, json=data, headers=headers)
print(req.text)
require 'net/http'
require 'json'

uri = URI("https://api.jsonbin.io/s")
res = Net::HTTP.start(uri.host, uri.port, use_ssl: true) do |http|
  req = Net::HTTP::Put.new(uri)
  req['secret-key'] = '<YOUR_SECRET_KEY>'

  http.request(req)
end

puts res.body
Request Response
Success
200
{
  "success":true,
  "data":{
    "$id": "https://example.com/geographical-location.schema.json",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "title": "Longitude and Latitude Values",
    "description": "A geographical coordinate.",
    "required": [ "latitude", "longitude" ],
    "type": "object",
    "properties": {
      "latitude": {
        "type": "number",
        "minimum": -90,
        "maximum": 90
      },
      "longitude": {
        "type": "number",
        "minimum": -180,
        "maximum": 180
      }
    }
  },
  "id":"<SCHEMA_ID>"
}
Error
401, 422
Status Code Error Message
401 Unauthorized
Need to provide a secret-key to READ Schema Document.

Fix: Ensure that you are passing secret-key header when Reading a Schema Doc.

422 Unprocessible Entity
Invalid Schema Document ID

Fix: You need to pass the correct Schema ID

401 Unauthorized
Invalid secret key provided.

Fix: Ensure that you are passing a valid secret-key in the headers.

422 Unprocessible Entity
Schema Documnent not found

Fix: Ensure that the Schema Doc ID you are passing is correct.