Runs & Results
List upstream calls (debug runs)
Inspect the timeline of every upstream HTTP interaction in an author debug run for troubleshooting.
GET
List upstream calls (debug runs)
GET https://api-datahub.octoparse.com/v1/runs/{run_id}/upstream-calls
Authentication: API key required, and only the app author (publisher) may call it. Everyone else gets 404.
Upstream-call timeline for debug runs (run_kind=test). For api-type runs, each upstream HTTP interaction (submit / status / fetch) is one entry. summary aggregates the full trail by (attempt, stage), independent of pagination, so you can see which stage is stuck at a glance. items carries metadata only; request and response bodies are loaded on demand from the single-call detail endpoint.
You can only read your own debug runs. Another account’s runs, missing runs, and production runs all return 404. Credential and environment values are redacted on write; values marked sensitive in the input contract are redacted again on read. Code-type runs have no HTTP trail and return an empty list.
Request
Path parameters
string
required
Debug run id.
Query parameters
integer
default:"0"
Pagination offset.Range ≥ 0.
integer
default:"50"
Page size.Range 1 to 500.
string
Filter to one stage.
submit submits work, status polls status, fetch retrieves data.Values: submit / status / fetch.Example request
Response
200 success
data. Fields:
string
required
—
object[]
required
Stats aggregated by (attempt, stage).
object[]
required
Call metadata entries.
object
required
Pagination object.
Errors
Error responses use
{"error": {code, category, message, retryable}}. See Errors.