REST queries
REST queries are configured in API Editor for a saved REST connection.
Create a query
- Open Workspace Settings > Connections > APIs
- Select your connection
- Click Open in API Editor
- Click Create new query
- Enter a clear query name
- Set HTTP method
- Enter endpoint path or full URL
- Configure Params, Headers, Body, and Bindings
- Select an auth config (if required)
- Click Send
- Validate response and schema
- Click Save Query
Query fields reference
| Area | What to configure | Notes |
|---|---|---|
| Method | GET, POST, PUT, PATCH, DELETE | Must match endpoint contract |
| URL/Path | Endpoint path or full URL | Usually path + connection base URL |
| Params | Query-string key/value pairs | Supports bindings |
| Headers | Request headers | Supports bindings and shared defaults |
| Body | Payload for write/query APIs | Use valid JSON/XML/Text as required |
| Auth selection | Connection auth config to apply | Choose per-query |
| Transformer | JavaScript response shaping | Re-test schema after changes |
Query lifecycle checklist
Before first use:
- Send query and confirm status code
- Validate response shape matches expected schema
- Save query
Before production use:
- Test with realistic runtime bindings
- Validate empty-state response behavior
- Validate error-state handling in app actions
Transformer example (flatten nested response)
const from = data.from
const to = data.to
return {
fromId: from.id,
fromSections: from.sections,
toId: to.id,
toSections: to.sections,
}After applying a transformer:
- Click Send.
- Confirm schema fields.
- Save the query.
Common issues
401/403: wrong or missing auth config.404: wrong path or base URL.400/422: request payload does not match API contract.- Empty rows with
200: binding values not populated as expected. - Schema mismatch in app: query changed but app bindings not updated.
Related guides
Updated 2 days ago