Remote Data
The Remote Data field type lets editors work with data from an external HTTP API. Contismo fetches the API at edit time and either resolves live JSON on delivery (passthrough) or lets editors pick mapped options that are saved on the entry (select).
Use this when values should come from a live external source—product catalogs, CRM records, location lists, or any JSON API—rather than being typed manually.
Add a Remote Data Field
Section titled “Add a Remote Data Field”- Open Content Models or Taxonomies in the Studio.
- Edit the model and add a field.
- Choose Remote Data as the field type.
- Configure the request and response settings (see below).
- Click Test Connection to verify the API responds as expected.
- Save the model.
Configure the Request
Section titled “Configure the Request”Each Remote Data field needs a request configuration:
- Remote Data URL — the full URL that returns the data for this field.
- HTTP Method — GET or POST.
- Request Parameters (optional) — query string parameters appended to the URL.
- Request Headers (optional) — custom headers sent with the request. Mark a header as Is Private to store it as an encrypted secret.
- Basic Authentication (optional) — username and password for APIs that require HTTP basic auth.
Click Test Connection while designing the schema to confirm the API responds. A successful test shows a sample result and, when applicable, detected list paths in the response.
Response Modes
Section titled “Response Modes”Choose how the API response is used in the entry editor.
Passthrough
Section titled “Passthrough”Passthrough resolves the field value from the remote API when content is delivered—for example when queried through the GraphQL API.
- Response Path (optional) — dot notation path to extract part of the response instead of returning the full payload. For example,
data.itemsor0.titlewhen the root is an array.
In the entry editor, editors can open a preview of the current API response with View Data.
Select from Array
Section titled “Select from Array”Select from Array maps an array in the API response to dropdown options editors can pick from. The selected value or values are stored on the entry in the database.
Configure these paths (dot notation relative to the response root):
- List Location — path to the array of items (for example,
itemsordata.results). - Value Path — property on each item to store (for example,
id). - Label Path — property on each item to display (for example,
name). - Selection Type — Single or Multiple.
In the entry editor, options are fetched automatically when the entry is open. Editors choose one or more values from the mapped list.
Related
Section titled “Related”For a quick comparison of all field types, see Field Types.