> ## Documentation Index > Fetch the complete documentation index at: https://newscatcherinc-docs.mintlify.site/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get monitor status history > Returns the full execution history of a monitor as a list of status entries, ordered from newest to oldest. ## OpenAPI ````yaml catch-all-api get /catchAll/monitors/{monitor_id}/status openapi: 3.1.0 info: title: NewsCatcher CatchAll API version: 1.6.4 description: > CatchAll is a web search API that generates unique datasets that don't exist anywhere else on the web. Built on NewsCatcher's proprietary real-world event index, it delivers state-of-the-art recall—finding all relevant events, not just top results. ### Authentication All endpoints except /health and /version require `x-api-key` header. If the key is invalid or missing, the API returns the `403 Forbidden` error. ### Job workflow 1. (Optional) Get suggestions via /catchAll/initialize 2. Submit a query via /catchAll/submit with optional date ranges and custom validators/enrichments 3. Poll /catchAll/status/{job_id} until completed (10-15 minutes) 4. Retrieve results via /catchAll/pull/{job_id} ### Monitor workflow 1. Create successful job via /catchAll/submit 2. Create monitor via /catchAll/monitors/create with schedule 3. Retrieve aggregated results via /catchAll/monitors/pull/{monitor_id} ### Webhook workflow 1. Create a webhook via `POST /catchAll/webhooks` 2. Attach it to a job or monitor via `POST /catchAll/webhooks/{webhook_id}/resources`, or pass `webhook_ids` at job or monitor creation time 3. Receive HTTP notifications at the configured URL when each job completes ### Company search workflow 1. Create a dataset via `POST /catchAll/datasets/` or `POST /catchAll/datasets/upload` 2. Wait for the dataset `latest_status` to reach `ready` 3. Submit a job with `connected_dataset_ids` pointing to your dataset 4. Retrieve results — each record includes a `connected_entities` array with relevance scores per matched company ### Important notes **Dynamic schemas**: Response schemas are generated dynamically by LLMs. Field names in the `enrichment` object may vary and are not deterministic across jobs unless explicitly specified. contact: name: NewsCatcher url: https://newscatcherapi.com email: support@newscatcherapi.com servers: - url: https://catchall.newscatcherapi.com description: Production server security: - ApiKeyAuth: [] tags: - name: Jobs description: Operations to create, monitor, and retrieve job results. externalDocs: description: Learn about job lifecycle and status tracking url: >- https://www.newscatcherapi.com/docs/web-search-api/get-started/quickstart - name: Monitors description: Operations to create, operate and retrieve monitor results. externalDocs: description: >- Automate recurring queries with scheduled jobs and webhook notifications. url: >- https://www.newscatcherapi.com/docs/web-search-api/guides-and-concepts/monitors - name: Webhooks description: > Operations to create and manage reusable webhook endpoints. A webhook is a named HTTP endpoint that receives a POST notification when a job or monitor completes. Create webhooks once at the organization level and attach them to any number of jobs or monitors via `webhook_ids`. Supports Slack, Microsoft Teams, and generic HTTP targets with configurable delivery modes, authentication, and headers. externalDocs: description: Learn about centralized webhooks and notification setup url: >- https://www.newscatcherapi.com/docs/web-search-api/guides-and-concepts/webhooks - name: Entities description: > Operations to create, update, and delete company entities. Entities are the building blocks of Company Watchlist. Each entity represents a company (or person) you want to track. Add identifying information such as domain, alternative names, and key persons to improve matching quality. externalDocs: description: Learn about Company Watchlist and entities url: >- https://www.newscatcherapi.com/docs/web-search-api/guides-and-concepts/company-search - name: Datasets description: > Operations to create and manage datasets of entities. A dataset is a named collection of entities — think of it as a watchlist or portfolio. Connect a dataset to a job via `connected_dataset_ids` to activate Company Watchlist. Datasets can be reused across multiple jobs and monitors. externalDocs: description: Learn about datasets and Company Watchlist url: >- https://www.newscatcherapi.com/docs/web-search-api/guides-and-concepts/company-search - name: Projects description: | Operations to create, organize, and manage projects. A project is a named container for jobs, monitors, and datasets. Group related resources by use case, team, or client, and share them with teammates. Resources can be assigned at creation time or post-hoc. externalDocs: description: Learn about projects and resource organization url: >- https://www.newscatcherapi.com/docs/web-search-api/guides-and-concepts/projects - name: Meta description: Operations to check API health and version. externalDocs: description: Find out more about NewsCatcher CatchAll API url: https://www.newscatcherapi.com/docs/web-search-api/get-started/introduction paths: /catchAll/monitors/{monitor_id}/status: get: tags: - Monitors summary: Get monitor status history description: > Returns the full execution history of a monitor as a list of status entries, ordered from newest to oldest. operationId: getMonitorStatusHistory parameters: - name: monitor_id in: path required: true schema: type: string format: uuid description: Monitor identifier. responses: '200': $ref: '#/components/responses/MonitorStatusHistoryResponse' '401': $ref: '#/components/responses/UnauthorizedError' '404': $ref: '#/components/responses/NotFoundError' components: responses: MonitorStatusHistoryResponse: description: Monitor status history retrieved successfully. content: application/json: schema: $ref: '#/components/schemas/MonitorStatusHistoryResponseDto' example: success: true message: null monitor_id: a1b2c3d4-e5f6-7890-abcd-ef1234567890 total_statuses: 39 statuses: - status: disable created_at: '2026-02-06T00:42:00Z' additional_information: null - status: dump created_at: '2026-02-05T12:04:00Z' additional_information: nb_existing_records: 408 nb_final_records: 28 - status: scheduled created_at: '2026-02-05T12:00:00Z' additional_information: job_id: c3d4e5f6-a7b8-9012-cdef-345678901234 start_date: '2026-02-04T12:00:00' end_date: '2026-02-05T12:00:00' - status: created created_at: '2026-01-19T16:28:00Z' additional_information: null UnauthorizedError: description: API key is missing or invalid. content: application/json: schema: $ref: '#/components/schemas/Error' example: detail: X-API-Key header is required for this endpoint NotFoundError: description: Job/monitor not found or results not available content: application/json: schema: $ref: '#/components/schemas/Error' schemas: MonitorStatusHistoryResponseDto: type: object required: - success - monitor_id - total_statuses - statuses properties: success: type: boolean description: True if the request succeeded; false otherwise. example: true message: type: - string - 'null' description: Optional message. `null` on success. monitor_id: type: - string - 'null' format: uuid description: Monitor identifier. `null` on failure. example: a1b2c3d4-e5f6-7890-abcd-ef1234567890 total_statuses: type: - integer - 'null' description: Total number of status entries in the history. example: 39 statuses: type: - array - 'null' items: $ref: '#/components/schemas/MonitorStatusEntry' description: Full status history, ordered newest to oldest. Error: type: object properties: detail: type: string description: Error message. example: Invalid API key MonitorStatusEntry: type: object required: - status - created_at properties: status: type: string enum: - created - enable - disable - scheduled - dump description: | Type of lifecycle event. - `created`: Monitor was created. - `enable`: Monitor was enabled. - `disable`: Monitor was disabled. - `scheduled`: A job was triggered for execution. `additional_information` contains `job_id`, `start_date`, and `end_date`. - `dump`: Results were collected after a job completed. `additional_information` contains `nb_existing_records`, `nb_final_records`, and optionally `webhook`. created_at: type: string format: date-time description: Timestamp of this event in ISO 8601 format with UTC timezone. example: '2026-02-05T12:04:00Z' additional_information: type: - object - 'null' description: > Event-specific metadata. `null` for `created`, `enable`, and `disable` events. For `scheduled`: ```json { "job_id": "c3d4e5f6-a7b8-9012-cdef-345678901234", "start_date": "2026-02-04T12:00:00", "end_date": "2026-02-05T12:00:00" } ``` For `dump`: ```json { "nb_existing_records": 408, "nb_final_records": 28, "webhook": { "success": true, "status_code": 200, "error_message": null } } ``` The `webhook` key is only present if the monitor has a webhook configured. securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: API key for authentication. ````