Skip to content

Notes, Search & Pagination API

Practise create-read-update-delete, search boxes and infinite scrolling against a real HTTP API.

Three things every app does and every beginner gets stuck on: saving and editing records, a search box, and loading more items when the user scrolls. These endpoints let you practise all three. /notes answers GET, POST, PUT, PATCH and DELETE like a real backend (nothing is saved), /search searches movies, books, recipes and news at once, and the two pagination endpoints show the two common styles side by side.

Base URL https://toolorca.com/api/v1 No key · CORS open · JSON · conventions and limits

Endpoints

GET /api/v1/notes #

40 notes with title, content, colour, pinned and archived flags and tags.

Parameter In Type Description
userId / pinned / archived / color / tag query string Filters, e.g. pinned=true.
q query string Full-text search in the main text fields.
sortBy query string Field to sort by, e.g. price or rating.rate.
order query string asc (default) or desc.
select query string Comma-separated fields to return, e.g. title,price (id is always included).
limit query integer Items per page (default 30, max 100). 0 returns the maximum.
skip query integer Items to skip, for offset pagination.
page query integer 1-based page number; used when skip is not given.
curl 'https://toolorca.com/api/v1/notes?pinned=true&limit=2'
GET /notes?pinned=true&limit=2
Example response
{
  "data": [
    {
      "id": 1,
      "userId": 1,
      "title": "Study plan",
      "content": "Buy rice, eggs and morning glory.",
      "color": "yellow",
      "pinned": true,
      "archived": false,
      "tags": [
        "work"
      ],
      "createdAt": "2025-06-26T10:09:28Z",
      "updatedAt": "2025-07-14T10:09:28Z"
    },
    {
      "id": 2,
      "userId": 2,
      "title": "App feature ideas",
      "content": "Finish the login screen and test on a small phone.",
      "color": "purple",
      "pinned": true,
      "archived": false,
      "tags": [
        "study"
      ],
      "createdAt": "2025-11-12T21:16:42Z",
      "updatedAt": "2025-11-22T21:16:42Z"
    }
  ],
  "meta": {
    "total": 9,
    "limit": 2,
    "skip": 0,
    "page": 1,
    "pages": 5
  }
}

GET /api/v1/notes/{id} #

One note.

Parameter In Type Description
id required path integer The note id.
curl 'https://toolorca.com/api/v1/notes/1'
GET /notes/1
Example response
{
  "id": 1,
  "userId": 1,
  "title": "Study plan",
  "content": "Buy rice, eggs and morning glory.",
  "color": "yellow",
  "pinned": true,
  "archived": false,
  "tags": [
    "work"
  ],
  "createdAt": "2025-06-26T10:09:28Z",
  "updatedAt": "2025-07-14T10:09:28Z"
}

POST /api/v1/notes #

Create a note. Returns 201 with the new id. Nothing is saved: the response shows what a real API would return, and the data stays the same for everyone.

Parameter In Type Description
title required body string Note title.
content / color / pinned / tags body any Optional fields.
curl -X POST 'https://toolorca.com/api/v1/notes' \
  -H 'Content-Type: application/json' \
  -d '{"title":"Buy Kampot pepper","content":"Two bags for the office","color":"green","tags":["shopping"]}'
POST /notes
Example response (201)
{
  "id": 41,
  "content": "Two bags for the office",
  "color": "green",
  "pinned": false,
  "archived": false,
  "tags": [
    "shopping"
  ],
  "title": "Buy Kampot pepper",
  "createdAt": "2026-11-21T19:15:57Z"
}

PATCH /api/v1/notes/{id} #

Change some fields (PUT replaces the whole note and needs a title).

Parameter In Type Description
id required path integer The note id.
… body any Fields to change.
curl -X PATCH 'https://toolorca.com/api/v1/notes/1' \
  -H 'Content-Type: application/json' \
  -d '{"pinned":false,"color":"blue"}'
PATCH /notes/1
Example response
{
  "content": "Buy rice, eggs and morning glory.",
  "color": "blue",
  "pinned": false,
  "archived": false,
  "tags": [
    "work"
  ],
  "id": 1,
  "userId": 1,
  "title": "Study plan",
  "createdAt": "2025-06-26T10:09:28Z",
  "updatedAt": "2026-11-21T19:15:57Z"
}

DELETE /api/v1/notes/{id} #

Delete a note: returns it with isDeleted: true.

Parameter In Type Description
id required path integer The note id.
curl -X DELETE 'https://toolorca.com/api/v1/notes/2'
DELETE /notes/2
Example response
{
  "id": 2,
  "userId": 2,
  "title": "App feature ideas",
  "content": "Finish the login screen and test on a small phone.",
  "color": "purple",
  "pinned": true,
  "archived": false,
  "tags": [
    "study"
  ],
  "createdAt": "2025-11-12T21:16:42Z",
  "updatedAt": "2025-11-22T21:16:42Z",
  "isDeleted": true,
  "deletedAt": "2026-11-21T19:15:57Z"
}

GET /api/v1/pagination/offset #

Page-number pagination over 500 items, with meta, a Link header (first, prev, next, last) and X-Total-Count.

Parameter In Type Description
group query string alpha, beta, gamma or delta.
limit query integer Items per page (default 30, max 100). 0 returns the maximum.
skip query integer Items to skip, for offset pagination.
page query integer 1-based page number; used when skip is not given.
curl 'https://toolorca.com/api/v1/pagination/offset?page=2&limit=5'
GET /pagination/offset?page=2&limit=5
Example response
{
  "data": [
    {
      "id": 6,
      "name": "Item 6",
      "group": "beta"
    },
    {
      "id": 7,
      "name": "Item 7",
      "group": "gamma"
    },
    {
      "id": 8,
      "name": "Item 8",
      "group": "delta"
    },
    "… 2 more"
  ],
  "meta": {
    "total": 500,
    "limit": 5,
    "skip": 5,
    "page": 2,
    "pages": 100,
    "hasNext": true,
    "hasPrev": true
  }
}

GET /api/v1/pagination/cursor #

Cursor pagination for infinite scrolling: pass nextCursor back as cursor until hasMore is false.

Parameter In Type Description
cursor query string The nextCursor from the previous page (omit for the first page).
limit query integer 1 to 100 (default 10).
curl 'https://toolorca.com/api/v1/pagination/cursor?limit=5'
GET /pagination/cursor?limit=5
Example response
{
  "data": [
    {
      "id": 1,
      "name": "Item 1",
      "group": "alpha"
    },
    {
      "id": 2,
      "name": "Item 2",
      "group": "beta"
    },
    {
      "id": 3,
      "name": "Item 3",
      "group": "gamma"
    },
    "… 2 more"
  ],
  "nextCursor": "eyJhZnRlciI6NX0",
  "hasMore": true,
  "limit": 5
}

Offset or cursor?

Offset pagination (page and limit) is simple and lets users jump to page 7, but items can repeat or go missing when the list changes between requests. Cursor pagination only goes forward from the last item you saw, which is what feeds and chat histories use. Try both: build a numbered pager with /pagination/offset and an infinite list with /pagination/cursor.

Free daily limit

Shared with the other mock services: 50 requests per day and 10 per minute per IP address. For unlimited CRUD practice the todos and posts endpoints have a higher limit.

Frequently asked questions

Why does my new note disappear?

Nothing is saved, so every user sees the same data. Keep created notes in your app’s state, as you would with an optimistic update.

What does the Link header look like?

<…/pagination/offset?page=3&limit=5>; rel="next", plus first, prev and last. Many HTTP libraries can parse it for you.

Can I read the Link header from a browser?

Yes. It is listed in Access-Control-Expose-Headers, together with X-Total-Count and the rate-limit headers.

Is the cursor secret?

No, it is just base64url-encoded JSON. Treat it as an opaque string anyway: real APIs change their cursor format.

More free APIs