Online REST API for Testing and Prototyping

fake data | real responses | 24/7 online

Trying it Out

POST /public/v1/usersCreate a new user
GET /public/v1/users/123Get user details
PUT|PATCH /public/v1/users/123Update user details
DELETE /public/v1/users/123Delete user

Nested Resources

GET /public/v1/users/123/postsRetrieves user posts
GET /public/v1/posts/123/commentsRetrieves post comments
GET /public/v1/users/123/todosRetrieves user todos
POST /public/v1/users/123/postsCreates a user post
POST /public/v1/posts/123/commentsCreates a post comment
POST /public/v1/users/123/todosCreates a user todo



Unlike Web applications, RESTful APIs are usually stateless, which means sessions or cookies should not be used. Therefore, each request should come with some sort of authentication credentials. A common practice is to send a secret access token with each request to authenticate the user. Since an access token can be used to uniquely identify and authenticate a user, API requests should always be sent via HTTPS to prevent man-in-the-middle (MitM) attacks.

There are different ways to send an access token:

cUrl Examples

1. List users
curl -i -H "Accept:application/json" -H "Content-Type:application/json" -XGET ""
2. Create user
curl -i -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization: Bearer ACCESS-TOKEN" -XPOST "" -d '{"name":"Tenali Ramakrishna", "gender":"male", "email":"", "status":"active"}'
3. Update user
curl -i -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization: Bearer ACCESS-TOKEN" -XPATCH "" -d '{"name":"Allasani Peddana", "email":"", "status":"active"}'
4. Delete user
curl -i -H "Accept:application/json" -H "Content-Type:application/json" -H "Authorization: Bearer ACCESS-TOKEN" -XDELETE ""

Http Response Codes Summary