Get
Returns one job: its status, how many targets it affected, whether Oleria’s own data reflects the change yet, and whether it can still be reverted. Poll this after a write until the status is terminal. Requires the https://devx.{environment}.oleria.io/read scope.
Authorizations
OAuth 2.0 client-credentials flow. Request an access token from the token endpoint and send it as Authorization: Bearer <token>.
Path Parameters
Id of the job, as returned by the write that created it.
Response
The action job.
One submitted change and the outcome of applying it.
Id of this job.
"9f2b1c7e-5a84-4d6b-9c31-0e7f8a2d4b16"
When the job was accepted.
Where the job has got to. Queued and Running are not terminal; every other value is.
Queued, Running, Completed, PartiallyCompleted, Failed, Cancelled, Reverted, PartiallyReverted How many targets the change was applied to, and how they turned out. Targets still in flight are the remainder. Some changes expand server-side into the records that actually have to be altered, so these counts are not final while the status is Queued. A total of zero there means the target set is still being resolved, not that there is nothing to do.
Whether this job applied a change or undid one. A revert cannot itself be reverted, so this is what tells a caller which jobs are candidates.
Change, Revert When the job reached a terminal status; null while it is still running.
Whether Oleria's own data reflects this change yet. A job can be complete, with the change applied in the application, while reads here still return the previous value.
The operation that started this job, named as it appears in this API (for example DisableAccount). Absent for changes made through the Oleria application rather than through this API, which have no operation to name.
"DisableAccount"
Whether this job's change can still be undone.
The revert job that undid this one. Null until this job has been reverted, which makes the pair navigable from either end.
The job this one undoes. Set when type is Revert, null otherwise.

