1. jsonbin(1)
  2. json RESTful store
  3. jsonbin(1)


jsonbin.org - A personal JSON store as a RESTful service


curl https://jsonbin.org/remy/blog


To save data, you'll first need to sign in to get an API key. All examples below use example as the username.


jsonbin.org is a personal key/value JSON store as a service. Protected behind authentication and API key requests, data is stored as JSON and can be deep linked. A permissioning model also allows specific paths to your store to become public to share with others.

The aim of the project is to provide a simplified data store for tinkerers.

Important: jsonbin is currently in open beta. If you have questions, please get in touch.


By default all user store data is protected behind auth either via browser sign in, or an authorization token. The token is your apikey. For example:

curl -X POST https://jsonbin.org/example/blog \
     -H 'authorization: token abcd-xyz-123' \
     -d '{ url: "https://remysharp.com" }'

To use jsonbin in the browser, it's recommended that you use a bearer token with a limited expiry:

fetch('https://jsonbin.org/me/urls', {
  headers: {
    // example uses 1 minute token restricted to `urls` path
    authorization: 'Bearer [token]',
}).then(res => res.json()).then(res => {


A private namespace URL "_" is used for jsonbin specific endpoints:

The following methods with your authorization header will access your data store:

  • GET return given path mapped to a JSON path.
  • POST store the payload (supports JSON and files).
  • PATCH merge the payload with the endpoint.
  • DELETE store path.

For example:

curl -X PATCH \
     -H 'authorization: token abcd-xyz-123' \
     -d'{ "topic": "code" }' \

By default all endpoints are private, but you can modify a specific entry point to be public by default by changing the permissions:

  • PUT /example/:path/_perms make the :path public.
  • DELETE /example/:path/_perms make :path private.
  • GET /example/:path/_perms check permissions of :path.

Public endpoints accept GET requests without the authorization header.

Notes on PATCH

The PATCH method implements the JSON Merge Patch standard (RFC 7396) when the target endpoint is an object. This means if you wish to remove a property from your store, a value of null is sent:

curl -X PATCH \
     -H 'authorization: token abcd-xyz-123' \
     -d'{ "title": null }' \

The exception is that when the endpoint is an array, a PATCH will always push onto the endpoint. If you need to reset the array you can POST to the endpoint, or you can DELETE an individual array element.

Example storing files

You can use jsonbin as a shared clipboard across machines. Creating an alias to upload STDIN via curl could be posted to a public URL:

alias jsonbin="curl -X 'POST' \
      -H'authorization: token abcd-xyz-123' \
      -F'content=@-' \
echo "foo" | jsonbin

Example with arrays

As well as objects, arrays are also supported. To delete an array element, it should be accessed using the index as per:

curl -X DELETE https://jsonbin.org/example/urls/1

To push a new element, so long as the endpoint contains an array:

curl -X PATCH https://jsonbin.org/example/urls \
     -d "foo.com"


This project lives at jsonbin. Please report bugs to jsonbin/issues.


Remy Sharp <remy@leftlogic.com>

  1. V2.6.4
  2. January 2017
  3. jsonbin(1)