configs — one entry per resource batch, each with its
own status, progress, record counters (created / updated / deleted / skipped)
and error state. Reach for it after list_imports surfaces a run whose outcome
you need to explain, e.g. why an integration refresh failed. You only see
imports that touched a resource type you may read; an import whose every
resource type is outside your permissions is reported as not found.
Parameters
Body
Body
string
required
Id of the import to inspect — the id returned by list_imports.
Response
Body
Body
string
string
Deep link that opens this import expanded in the Qobra web app, on the
history page of a resource type it touched. Null only for an import with no
batch yet, which no history page lists.
string
Overall status: ‘scheduled’, ‘started’ or ‘finished’. One of:
scheduled,
started, finished.string
What kicked the import off, e.g. ‘scheduled_refresh’, ‘integration_refresh’
or ‘quota_sync’. Null when unknown. One of:
scheduled_refresh,
integration_refresh, integrations_with_frequency_refresh,
braqoffice_refresh, users_creation, user_integration_sync,
user_file_import_refresh, user_attributes_creation, groups_creation,
data_table_refresh, data_table_settings_update, field_creation,
quota_creation, quota_sync, quota_refresh, quota_settings_update.integer
Overall completion 0–100, averaged across the import’s batches (100 when it
has no batch).
boolean
True when any batch in the import ended in error.
string[]
Distinct resource types the import touched — any of ‘data_table’, ‘quota’,
‘user’.
object
The user who triggered the import; null for a system or scheduled import.
string
string
string
object[]
Per-batch breakdown of the import — one entry per resource batch, each with
its own status, progress, record counters and error state.