Read an extract configuration
This endpoint retrieves the extract configuration by name: the caller’s own draft under that name if they have one, and otherwise the submitted configuration that is still active.
The response carries status of the extract configuration, whether it is a draft, active or inactive, and version, which may be sent back on an update as a precondition.
Permissions for nested calls. This endpoint calls other Fynapse services with your token. Depending on the request, the token also needs:
data_structure_read, when the configuration names an entity.
Authentication
OAuth authentication of the form <token>.
Path parameters
Response
Format of the extracted data. Which values are allowed depends on uploadSpace.
On a read, what the configuration is doing. On a write, the status it should be in: DRAFT keeps it a draft, and anything else submits it.
The values a read returns are accepted on a write, so a configuration can be read, changed and sent back without translating them, and SUBMITTED is accepted as well because that is what submitting is called everywhere else.
On an update, omitting it leaves the configuration in the status it is in; a status this API does not know is refused with 400 rather than ignored.
The version the configuration is on. Send it back as expectedVersion on an update to fail safely when someone else has changed it in the meantime.
Whether late-arriving data is held back until a new group begins.
What is selected - the entity and namespace, the fields, filters, aggregations and clustering. The same shape the bulk configuration document uses for an extract configuration’s query.
When the extract runs - a frequency or a cron expression, or disabled. Validated when the configuration is submitted, not while it is a draft.