> ## 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. # Health-probe history of my apps > What the platform's daily health probe found on the apps I publish, most recent first: for each probed example, whether it still connected and produced records (PASS), produced nothing (NO_DATA), failed (FAIL, with the error), ran out of the probe budget (TIMEOUT) or was not run at all (SKIPPED: `skip_reason` = no-example / paused / not-eligible). Only published public or shared apps are probed; private apps never are. Probe runs never count in usage or billing and do not appear under GET /publisher/runs. Unknown or other people's apps in `data_app` are 404 (no existence leak). ## OpenAPI ````yaml /jp/datahub/api/openapi.json get /v1/publisher/probes 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: get: tags: - Publishing summary: Health-probe history of my apps description: |- What the platform's daily health probe found on the apps I publish, most recent first: for each probed example, whether it still connected and produced records (PASS), produced nothing (NO_DATA), failed (FAIL, with the error), ran out of the probe budget (TIMEOUT) or was not run at all (SKIPPED: `skip_reason` = no-example / paused / not-eligible). Only published public or shared apps are probed; private apps never are. Probe runs never count in usage or billing and do not appear under GET /publisher/runs. Unknown or other people's apps in `data_app` are 404 (no existence leak). operationId: publisher_probes_v1_publisher_probes_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 - name: days in: query required: false schema: type: integer maximum: 365 minimum: 1 description: look-back window in days (default 30) default: 30 title: Days description: look-back window in days (default 30) - name: limit in: query required: false schema: type: integer maximum: 500 minimum: 1 default: 100 title: Limit responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/DataEnvelope_PublisherProbeList_' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' components: schemas: DataEnvelope_PublisherProbeList_: properties: data: $ref: '#/components/schemas/PublisherProbeList' type: object required: - data title: DataEnvelope[PublisherProbeList] HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError PublisherProbeList: properties: items: items: $ref: '#/components/schemas/PublisherProbe' type: array title: Items type: object title: PublisherProbeList description: Probe history of my apps, most recent first. 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 PublisherProbe: 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: '' example_id: type: string title: Example Id default: '-' verdict: type: string title: Verdict skip_reason: anyOf: - type: string - type: 'null' title: Skip Reason records: anyOf: - type: integer - type: 'null' title: Records duration_ms: anyOf: - type: integer - type: 'null' title: Duration Ms error: anyOf: - $ref: '#/components/schemas/PublisherRunError' - type: 'null' kind: anyOf: - type: string - type: 'null' title: Kind description: '`scheduled` (daily batch) or `manual` (ops re-test)' created_at: type: string title: Created At finished_at: anyOf: - type: string - type: 'null' title: Finished At type: object required: - verdict - created_at title: PublisherProbe description: |- One health-probe result of an app I publish (one example, one run of the platform's daily connectivity check): whether the example still produces records, how long it took and why it failed. Probe runs never count in usage or billing. 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 ````