One mapping table of a consumer: its rows, values and candidates
Changed onThe table's rows with their values, and one page of what a row may point at. Rows are what the source lists (or the fixed rows in use), then the keys an execution or a preview met without a value. Candidates are read from the consumer's connection: refresh reads them again, not from the connector's cache. The table's autofill rules run first, so a row they can fill has a value. Edit the values with PATCH /consumers/{consumer_id}/syncs/{syncid}.
Request
- Base URLhttps://api.chift.eu
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Query parameters
Keeps the candidates whose label or key contains it, ignoring case.
Page of candidates.
Candidates per page.
Every item of the target, not only the suggested ones.
The row (its source_key) to suggest candidates for: a table can suggest per row.
Read the rows and candidates from the connections again.
ISO 639-1 code of the language of the texts (en, fr, nl, de, es; any case), falling back to English. Without it, translation keys.
Response
Successful Response
Example response
{
"key": "spend_to_accounting.PurchaseVatCodes",
"rows": [
{
"source_key": "601000",
"label": "601000 Office supplies"
}
],
"candidates": {
"items": [
{
"key": "601000",
"label": "601000 Office supplies"
}
]
}
}Changes
- info
endpoint added
- info