Quickstart: push with the API
Index app content no crawler can see — records behind a login, per-user libraries, anything your own server already holds.
Use the API when your content is not a set of public pages: records behind a login, a per-user library, or anything generated by your own server. This is how Toread indexes each reader's library.
1. Create an index and a write key
From the dashboard, create an index and a write key (ingest only, cannot search). Keys are shown once — copy it now.
2. Push your first batch
Every record needs an objectID. Everything else is your own attributes — suo does not require a fixed schema. See Write records for the full request and response shape.
3. Search it
4. Add partitions for per-user content
If each reader should only ever see their own records, declare a partitionKey on the index (see Partitions) and mint a scoped token per reader from your own server. The widget or SDK then searches with that token instead of a shared key.
Keeping it in sync
Push on every write to your own database: when a record is created, changes, or is deleted. Pass version as your own updatedAt so a late or out-of-order write never overwrites a newer one — see Versions and last-writer-wins.
Next: read Push app content for the full per-user partition walkthrough, or the API reference for every route.