JSON KV
A key/value store you talk to with nothing but HTTP. Write a value to a key, read it back from a URL, and get JSON either way.
Waiting for request...
No client library. No schema. No signup. If you can make an HTTP request, you have a URL-backed value store.
Text. JSON. Files.
Text
/message
hello world
JSON
/config
{"theme":"dark"}
File
/image
image.png
HTTP API
| Method | Route | Purpose |
|---|---|---|
GET |
/:id |
Read the value stored under a key |
PUT |
/:id |
Store text, JSON, or files |
HEAD |
/:id |
Check whether a key exists |
DELETE |
/:id |
Remove a key and its data |
Built for simple persistence
Static sites
Add counters, settings, feature flags, or small pieces of state without building a backend.
Scripts
Give any machine persistence with a single HTTP request.
Webhooks
Remember events, payloads, and anything your webhook receives.
Prototypes
Move fast while your data model is still changing.
Storage behind the API
JSON KV
|
-----------------
| |
Redis Memory
production development
The API stays the same. The storage layer can change underneath.
Examples
# Store a value
curl -X PUT https://jsonkv.com/counter \
-d "42"
# Read it back
curl https://jsonkv.com/counter