[github-actions]

Automated sync of web-search-api/api-reference/fastapi-openapi.yml from https://catchall.newscatcherapi.com/openapi.json.

Review checklist:

• Diff looks expected — no accidental drops of descriptions or schema renames
• If new endpoints appear, note them (MDX pages will be needed — handled in Stage 2)
• If anything looks wrong, close this PR and fix it in the FastAPI service

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
newscatcherinc	🟢 Ready	View Preview	Oct 23, 2026, 8:45 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
newscatcherinc-docs	🟢 Ready	View Preview	Oct 23, 2026, 8:45 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[github-actions]

Docs update for v1.10.3 added to this branch (commit d9ecf11).

Auto-updated

• catch-all-api.yml: info.version 1.10.2 → 1.10.3. No schema changes.
• changelog.mdx: added the v1.10.3 entry at the top (updated models, more accurate deduplication, event monitor group dump fix).
• No guide pages changed. The existing deduplication wording in concepts/event-monitors.mdx and the how-to pages is still accurate.

Spec diff

• This snapshot matches the 2026-10-22 snapshot exactly (only key order changed). Both report 1.10.3.
• The 1.10.3 Notion page says "No schema, migration or endpoint changes". That answers the open question from the v1.10.2 PR (chore: sync FastAPI OAS + update docs for v1.10.2 #158): job_info / JobIterationInfo was already in the API before 1.10.3, so the "Search turn in job responses" section stays under 1.10.2.

Please review

• Long-standing drift between the live spec and the generated spec: some schemas and fields in fastapi-openapi.yml have no counterpart in catch-all-api.yml. Examples: sharing_info / Ownership, PullResponseDto.connected_dataset_ids, SubmitRequestDto.schema, CreateDatasetRequestDto.project_id, ListMonitorJobsResponseDto, RunInfoDto, DateRangeDto, WebhookDeliveryStatus, and several fields on ArticleRecordDto, MonitorRecordDto, and MonitorCitationDto. Some of these may be modeled differently on purpose in the live spec. None of it is new in 1.10.3, so I left it alone. It may be worth a separate sync pass.
• The Notion "Features" database is a linked view that the integration token can't read (it returns no data sources), so the changelog is based only on the main page's Business and Technical Impact sections.

Skipped (internal / not public API)

• Model and vendor names (Gemini 2.5 → DeepSeek V4.1 Flash) and the internal cost benchmark (~90% cheaper). The changelog only says "updated models". Models aren't exposed or documented anywhere in the public API.
• OpenRouter client, environment variables, Doppler and deploy steps, test additions, and release maintenance.

Decisions made

• Used the public term "event monitor group" for Notion's "monitor-group dump/summaries".
• Wrote the dedup changes as user-visible outcomes (no merging across jobs or monitors, records stay separate when a merge can't be verified, no dropped events on errors) and left out implementation details such as pair budgets and residual dedup.

Notion changelog: https://app.notion.com/p/newscatcherapi/1-10-3-3fab932ccbdc804b89ecc3a60029b938?source=copy_link

---

🤖 Generated with Claude Code