> ## 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 job status > Retrieve the current processing status of a job. ## OpenAPI ````yaml catch-all-api get /catchAll/status/{job_id} openapi: 3.1.0 info: title: NewsCatcher CatchAll API version: 1.6.3 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/status/{job_id}: get: tags: - Jobs summary: Get job status description: Retrieve the current processing status of a job. operationId: getJobStatus parameters: - $ref: '#/components/parameters/JobId' responses: '200': $ref: '#/components/responses/StatusResponse' '403': $ref: '#/components/responses/ForbiddenError' '404': $ref: '#/components/responses/NotFoundError' externalDocs: description: Understanding job statuses and polling url: >- https://www.newscatcherapi.com/docs/web-search-api/api-reference/jobs/get-job-status components: parameters: JobId: name: job_id in: path required: true description: > Unique job identifier returned from [`POST /catchAll/submit`](https://www.newscatcherapi.com/docs/web-search-api/api-reference/jobs/create-job). schema: type: string format: uuid example: 5f0c9087-85cb-4917-b3c7-e5a5eff73a0c responses: StatusResponse: description: Status retrieved successfully content: application/json: schema: $ref: '#/components/schemas/StatusResponseDto' example: job_id: 5f0c9087-85cb-4917-b3c7-e5a5eff73a0c status: completed steps: - status: submitted order: 1 completed: true - status: analyzing order: 2 completed: true - status: fetching order: 3 completed: true - status: clustering order: 4 completed: true - status: enriching order: 5 completed: true - status: completed order: 6 completed: true - status: failed order: 7 completed: false ForbiddenError: description: Invalid or missing API key content: application/json: schema: $ref: '#/components/schemas/Error' NotFoundError: description: Job/monitor not found or results not available content: application/json: schema: $ref: '#/components/schemas/Error' schemas: StatusResponseDto: type: object required: - job_id properties: job_id: type: string format: uuid description: Job identifier. example: 5f0c9087-85cb-4917-b3c7-e5a5eff73a0c status: allOf: - $ref: '#/components/schemas/PublicJobStatus' description: Current job processing status. steps: type: array items: $ref: '#/components/schemas/JobStep' description: > Detailed progress tracking for each processing stage. Steps progress sequentially from order 1 (submitted) through 5 (enriching), ending at order 6 (completed) or 7 (failed). Error: type: object properties: detail: type: string description: Error message. example: Invalid API key PublicJobStatus: type: string enum: - submitted - analyzing - fetching - clustering - enriching - completed - failed description: > Current job processing status. Jobs progress through these stages: - `submitted`: Job queued, waiting to start processing. - `analyzing`: Extracting keywords, generating search queries, and creating validators/extractors. - `fetching`: Retrieving web pages. - `clustering`: Grouping similar web pages into clusters. - `enriching`: Validating clusters and extracting structured data. - `completed`: Job finished successfully, results ready. - `failed`: Job processing failed. Poll `/catchAll/status/{job_id}` every 30-60 seconds until status is `completed` (typically 10-15 minutes). example: fetching JobStep: type: object required: - status - order - completed properties: status: $ref: '#/components/schemas/PublicJobStatus' order: type: integer description: Sequential position of this step in the pipeline (1-7). minimum: 1 maximum: 7 example: 2 completed: type: boolean default: false description: True if this step has finished processing; false otherwise. securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: API key for authentication. ````