QuickLookup
QuickLookup publishes and queries three kinds of data service:
- Time series return observations at a declared time grain.
- Event feeds return event occurrences with arbitrary start and end times.
- Lookups resolve supplied values such as coordinates, identifiers, or place names.
Time-series observations and events can be stored in QuickLookup's local ClickHouse, or read on demand from an approved CTX source. Customers choose the privacy policy. Account assignment comes from the signed-in identity and is not a form or API field.
Start with your task
-
Store time-series data
Define the measurements, publish a private series, add observations, and query them.
-
Store events
Define an event feed, publish it, add occurrences with stable identities, and query it.
-
Find and query a service
Search the catalogue, inspect the published contract, and run a request in the page.
-
Resolve a place, read its day
Turn a name, an address, coordinates, an IP, a phone number or a domain into a place, then read every source that a place and a date can answer, in one call.
-
Publish a grouped service
Present several compatible time series as one product with a series selector.
-
Publish a lookup
Expose an approved lookup source through a bounded, typed contract.
-
Use the API
Read the role-scoped OpenAPI contract and execute permitted operations inside the docs.
Before you create anything
- Search the catalogue for an existing entity, unit, metric, dimension, source binding, or contract. Reuse it when the meaning matches.
- Choose
storedonly when QuickLookup will own the rows. Chooseon_demandfor an approved adapter, including CTX FDW relations. - Choose the service's access policy.
Localis private; sharing policies still require consumer entitlements. - Save the draft, clear its readiness checks, and publish. Do not add stored rows until
the publication is
delivered.
Key terms
A time series or event feed is a published service definition. A data point is an observation belonging to a time series; it is not another service type. An event occurrence belongs to an event feed. See Data and service model for the full model.
Use Troubleshooting when a form is read-only, publication does not complete, a source is unavailable, or an API request is rejected.