> ## Documentation Index > Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Latest health-probe status of each of my apps > The most recent probe batch of each of my apps, folded to one app-level verdict (FAIL if any example failed, then TIMEOUT, NO_DATA, PENDING while the batch is still running, PASS when every example passed, SKIPPED when nothing was run) with the first failing example's error — the signal behind "is anything broken right now". Apps that were never probed are absent. Sorted worst first, then by app name. ## OpenAPI ````yaml /jp/datahub/api/openapi.json get /v1/publisher/probes/latest openapi: 3.1.0 info: title: DataHub API version: 0.2.0 description: Public /v1 contract of Octoparse DataHub. Internal channels are excluded. servers: - url: https://api-datahub.octoparse.com security: - bearerAuth: [] tags: - name: Discovery description: >- Anonymous access: platform metadata (currency), data app search, detail and input contract, machine-readable manifest spec. - name: Publishing description: >- Self-service publishing channel (API Key auth), two-phase: validate first (validate / package, nothing persisted), then publish (POST /data-apps, the submission goes live as a new Release). api kind (declarative integration) becomes visible on publish; code kind (code package) returns 202 and enters an async image build; once ready it is promoted to a Release, visible and runnable. Poll progress via GET /data-apps/{ref}/builds. - name: Runs & Results description: >- Start / query / cancel runs and read result records with pagination. Business inputs go in the request body; platform run options (wait, max_records) go in query parameters. - name: Datasets description: >- Metadata and record access for platform datasets (including seeded stock data). - name: Account description: Account info and cumulative usage for the current API Key. - name: Secrets description: >- CRUD for upstream credentials (environment entries referenced by manifest `runtime.env`). Plaintext is write-only: every read returns a mask. paths: /v1/publisher/probes/latest: get: tags: - Publishing summary: Latest health-probe status of each of my apps description: |- The most recent probe batch of each of my apps, folded to one app-level verdict (FAIL if any example failed, then TIMEOUT, NO_DATA, PENDING while the batch is still running, PASS when every example passed, SKIPPED when nothing was run) with the first failing example's error — the signal behind "is anything broken right now". Apps that were never probed are absent. Sorted worst first, then by app name. operationId: publisher_probes_latest_v1_publisher_probes_latest_get parameters: - name: data_app in: query required: false schema: anyOf: - items: type: string type: array - type: 'null' description: >- restrict to these apps (`/`, repeatable); default = all my apps title: Data App description: >- restrict to these apps (`/`, repeatable); default = all my apps responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/DataEnvelope_PublisherProbeStatusList_' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' components: schemas: DataEnvelope_PublisherProbeStatusList_: properties: data: $ref: '#/components/schemas/PublisherProbeStatusList' type: object required: - data title: DataEnvelope[PublisherProbeStatusList] HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError PublisherProbeStatusList: properties: items: items: $ref: '#/components/schemas/PublisherProbeStatus' type: array title: Items type: object title: PublisherProbeStatusList description: |- Latest probe status of each of my apps that has ever been probed (apps never probed are absent). ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type input: title: Input ctx: type: object title: Context type: object required: - loc - msg - type title: ValidationError PublisherProbeStatus: properties: namespace: anyOf: - type: string - type: 'null' title: Namespace app_name: type: string title: App Name default: '' app_version: type: string title: App Version default: '' verdict: type: string title: Verdict skip_reason: anyOf: - type: string - type: 'null' title: Skip Reason examples: type: integer title: Examples default: 0 passed: type: integer title: Passed default: 0 error: anyOf: - $ref: '#/components/schemas/PublisherRunError' - type: 'null' kind: anyOf: - type: string - type: 'null' title: Kind checked_at: type: string title: Checked At finished_at: anyOf: - type: string - type: 'null' title: Finished At type: object required: - verdict - checked_at title: PublisherProbeStatus description: |- The latest probe batch of one app, folded to an app-level verdict: FAIL if any example failed, then TIMEOUT, NO_DATA, PENDING (batch still running), PASS when every example passed, SKIPPED when no run was made (`skip_reason` says why). `error` is the first failing example's error. PublisherRunError: properties: code: type: string title: Code category: type: string title: Category default: internal message: type: string title: Message default: '' retryable: type: boolean title: Retryable default: false type: object required: - code title: PublisherRunError description: |- Why a run failed, as the publisher may see it: code, category, the message and whether the caller could retry. Field-level `details` of input validation and retry hints stay with the caller. securitySchemes: bearerAuth: type: http scheme: bearer description: DataHub API Key ````