api docs   •   examples

Demo apps, mock ups, proofs of concept... Sometimes we just need a quick way to persist some data, like configuration or user preferences, without getting into creating a dedicated data store. Or maybe we just don't want to pollute an existing storage with temporary data that is ephermal in nature and we only need for a short little while.

Well, say hello to prefs.us!

For reading written data you will need a key that was returned with the corresponding /write/? call.

Each /write/? call will return a key for subsequent reuse i.e. data retrieval, update, etc.

You can create keys ahead of time OR ... you can reuse keys autogenerated when calling /write/? endpoint without supplying a key - one will be generated for you and included in the response.