Publishing
Publisher latency
Run-duration percentiles for your apps (p50 / p90 / p95 / p99 / max), optionally broken down by app or version.
GET
Publisher latency
GET https://api-datahub.octoparse.com/v1/publisher/usage/latency
Authentication: API key required (Authorization: Bearer <API Key>).
Run duration for your apps: p50 / p90 / p95 / p99 / max of finished_at - started_at (milliseconds) over a bounded range, optionally broken down by app or by version (slowest p95 first). Ownership, range, and filter semantics match Publisher usage. Samples are every finished run that has a start time (including failures and cancellations—the distribution describes the runs themselves, not only successes). Percentiles are null when there are no samples. Percentiles need run details, so both bounds are required and the span must be at most 92 days.
Request
Query parameters
string
Optional single dimension:
data_app by app, version by version. Default returns range totals only.string[]
Limit to these apps. Repeatable.
string
Inclusive start. Required.
string
Exclusive end. Required.
string
Limit to one call channel.
boolean
default:"False"
Whether to include author debug runs.
Example request
Response
200 success
data. Fields:
object
required
The range actually used.
object
required
Range totals:
samples and each percentile in milliseconds.string
Dimension actually used, or omitted/empty when totals only.
object[]
Group rows with the same metrics plus dimension keys.
Errors
Error responses use
{"error": {code, category, message, retryable}}. See Errors.