OrdinateDB

Documentation

product Pre-releaseunwritten sections are marked
GET/v1/jobs

List storage jobs

operation ID: get_v1_jobs

Overview

List storage jobs. Collector and job operations expose ingestion diagnostics and managed storage work.

When to use it

  • Use it when an application needs to list storage jobs.
  • Use it when an operator is monitoring data ingestion or coordinating a storage-maintenance workflow.

Quick example

Set the base URL and replace generated identifiers or credentials with values from your installation.

cURL

curl --request GET \
  --url "$ORDINATE_URL/v1/jobs" \
  --header "Authorization: Bearer $ORDINATE_TOKEN"

Expected output · 200

Job ledger

Example 200 output

[
  {
    "job_id": 0,
    "kind": "string",
    "state": "string",
    "params": "string",
    "progress": "string",
    "started_ns": 0,
    "updated_ns": 0,
    "finished_ns": 0,
    "error": "string"
  }
]

The cURL request supplies the documented path and query values and asks OrdinateDB to list storage jobs. The documented 200 response is job ledger.

How it works

These routes report server-managed collector or job state; collector writes themselves use the separate gRPC ingest contract.

Reference

Required capability
read
Authorization scope
held anywhere

Parameters

No parameters.

Request body

This operation has no request body.

Responses

200Job ledger

application/json

array

errorany ofrequired

any of

option 1

string

option 2

null
finished_nsany ofrequired

any of

option 1

integer

UTC Unix timestamp in nanoseconds

format: int64

option 2

null
job_idintegerrequired
format: int64
kindstringrequired
paramsstringrequired
progressstringrequired
started_nsany ofrequired

any of

option 1

integer

UTC Unix timestamp in nanoseconds

format: int64

option 2

null
statestringrequired
updated_nsany ofrequired

any of

option 1

integer

UTC Unix timestamp in nanoseconds

format: int64

option 2

null
unknown fields rejected

Example 200 output

[
  {
    "job_id": 0,
    "kind": "string",
    "state": "string",
    "params": "string",
    "progress": "string",
    "started_ns": 0,
    "updated_ns": 0,
    "finished_ns": 0,
    "error": "string"
  }
]
401Authentication required

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 401 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}
403Read capability is not granted

application/json

ErrorEnvelope
codestringrequired
correlation_idstringrequired
format: uuid
detailsobjectoptional
errorstringrequired

Example 403 output

{
  "error": "string",
  "code": "account-sealed",
  "correlation_id": "00000000-0000-4000-8000-000000000001"
}

Code examples

These examples are generated from the source contract. Replace the base URL, credentials, identifiers, and minimal generated values for your instance.

JavaScript

const ordinateUrl = "http://localhost:8080";
const token = "<bearer-token>";

const response = await fetch(`${ordinateUrl}/v1/jobs`, {
  method: "GET",
  headers: {
    Authorization: `Bearer ${token}`
  }
});

if (!response.ok) {
  throw new Error(`OrdinateDB returned ${response.status}: ${await response.text()}`);
}

const data = await response.json();
console.log(data);

Related topics