When to use it
Starting from nothing, importing a CSV, or any dataset you do not already keep somewhere else. It is the most capable source: every filter operator, sorting on any field, full-text search across text fields, and exact counts.
Setup
1. Create a resource and define its fields
Choose EndpointOS managed, name the resource, and add the fields you want. Nothing to connect and no credentials to manage.
2. Add records
Write them through the API, import a CSV, or push JSON to the ingest endpoint and let the schema be inferred from your payload.
What the API supports for this source
Generated from the same declaration the API enforces on every request, so it cannot promise something a request would be rejected for.
| Filtering | equals, not equal, one of, greater than, greater or equal, less than, less or equal on any declared field |
|---|---|
| Sorting | Any field, plus createdAt and updatedAt |
| Search (q) | Supported |
| Writes | create, update, delete |
| Paging | limit and offset |
| Record count | Exact: the total describes the filtered set |
Worth knowing first
- This is the only source where ad-hoc filtering, sorting and search all work today, because the data is ours to index.
- Very large filtered reads are bounded: past 50,000 candidate records a filtered request is refused with a clear error rather than degrading.
If something goes wrong
This resource is too large for ad-hoc filtering
Why: A filtered or searched read would have scanned more than 50,000 records, which is capped to keep response times predictable.
Fix: Narrow the filter, or page without one. For datasets this size, an external Postgres or BigQuery source is usually the better home.