> ## Documentation Index > Fetch the complete documentation index at: https://docs.getoneprofile.ai/llms.txt > Use this file to discover all available pages before exploring further. # Stop a table's LinkedIn watch > Stop the watch: it adds no one else and drops anyone waiting. The table and its rows stay, and it can be started again. ## OpenAPI ````yaml /openapi.json post /find-leads/tables/{table_id}/watch/stop/ openapi: 3.1.0 info: contact: email: support@getoneprofile.ai name: Oneprofile Support description: >- REST API reference for Oneprofile, the GTM data layer for your CRM. Manage tables, enrichments, and integrations. Authenticate with an API key to get started. termsOfService: https://www.getoneprofile.ai/terms title: API Reference | Oneprofile version: '0.0' servers: - url: https://api.getoneprofile.ai security: [] tags: - description: >- The docked AI Assistant: its general chat about the workspace and the product, streamed as Server-Sent Events, and the one list of a person's threads across every assistant, with pin, rename, delete and the search-to-table link. name: assistant - description: >- The messages a person keeps to send the assistant again: the ones the workspace saved and the ones that ship with the product, with save, rename, edit and delete. name: assistant-prompt - description: >- Granted workspace actions: what the AI Assistant proposed or applied in a conversation, the approve and dismiss decisions on each card, the workspace's approval threshold and default grants, and the eight verbs. name: workspace-actions - description: >- The Getting started checklist: a workspace's progress through the six steps from its first people search to its first launched sequence. name: onboarding - description: Senders, connected mailboxes, tags, and the Google connect flow. name: senders - description: The workspace do-not-contact list, enforced before every send. name: suppression - description: >- The workspace's recontact rule: how long before anyone hears from us again. name: contact_cooldown - description: 'Sequence authoring: the graph, the table-backed audience, previews.' name: sequences - description: >- The outbound agent behind a sequence: the voice it writes in, its per-message prompts, what it wrote and what people told it. name: outbound-agents - description: >- The LinkedIn channel: connecting an account to a sender, its safety limits and history, and the protocol the browser extension speaks. name: linkedin - description: >- The approval queue: everything waiting on a person across every sender and channel, and the workspace's manual or automatic modes per channel. name: outreach - description: 'The unified outreach inbox: threads, replies, labels, events.' name: inbox - description: 'The AI reply layer: workspace settings, drafts, and approval.' name: inbox-ai - description: Notification rules, per-user preferences, and the Slack connection. name: notifications - description: Endpoints for seeing all available integration types. name: integration-types - description: Endpoints for creating and managing integrations. name: integrations - description: Endpoints for the generic OAuth install/claim app-listings engine. name: app-listings - description: Endpoints for creating and managing API keys. name: apikey - description: >- The Model Context Protocol endpoint: use Oneprofile from Claude Code, Claude Desktop, Cursor or any other MCP client, with an API key as the bearer token. name: mcp - description: Endpoints for managing billing and subscription information. name: billing - description: Endpoints for creating and managing tables. name: tables - description: Endpoints for table columns, formula previews, and on-demand column runs. name: table-columns - description: Endpoints for table rows and manual cell edits. name: table-rows - description: Endpoints for observing and cancelling table recompute runs. name: table-runs - description: >- Endpoints for org-shared per-column display preferences: hidden, pinned, width, and colour tint. name: table-ui-prefs - description: >- Endpoints for the org-shared names given to the column tint palette: what this organisation calls each colour. Org-level, not per-table. name: table-column-color-labels - description: >- Endpoints for the enrichment action catalog, model list, presets, draft generation, and saved agents. name: table-enrichments - description: >- Endpoints for teaching a saved agent from example rows: training sessions, per-row feedback, and the proposed prompt to approve. name: agent-training - description: >- The durable audit trail of a table's enrichment actions: configured, edited, run, cancelled, and settled cost. name: table-enrichment-audit-logs - description: Endpoints for saving and applying column templates. name: table-templates - description: Server-sent change feed for a table's grid. name: table-events - description: 'Endpoints for org-shared saved table views: sort, filters, hidden columns.' name: table-views - description: >- Endpoints for PER-USER table preferences: favourites and recently opened. Unlike the rest of the table surface these are personal, so two members of one organisation legitimately see different answers. name: table-user-prefs - description: >- Endpoints for building a table from an uploaded CSV: upload and preview the inferred columns, commit the reviewed mapping, then poll the row load. name: table-imports - description: Endpoint for downloading a table's rows as CSV. name: table-export - description: >- Endpoints for the integration a table imports from: attach and preview it, promote imported fields into columns, and run the import on demand. name: table-sources - description: >- Endpoints for a table's recurring import cadence: set it, pause it, and read the next fire times. name: table-schedules - description: >- Endpoints for pushing a table's rows out to a connected integration: list writable destinations, derive their write capabilities, and map export columns. name: table-writeback - description: >- Endpoints backing a lookup column's setup: the connections whose records a column could read, and the identity fields one record type can be looked up by. name: table-integration-lookup - description: >- Endpoints for sourcing leads from the lead database: count and preview matches, land them in a table, and keep saved searches. Alongside people and company searches, leads can be sourced from buying signals (what a company or person just did), with a catalogue endpoint behind the picker that builds them. name: find-leads - description: >- Endpoints for discovering a domain's subdomains from public certificate logs and landing the results in a table. name: find-subdomains - description: Endpoints for the credit balance meter and usage reporting. name: credits - description: >- Endpoints for the workspace referral program: the shareable link, the friends who joined through it, and claiming a code after signup. name: referral - description: >- Endpoints for the affiliate program's own dashboard: enrolling and claiming a code, the summary, stats and activity feed, the commission ledger, and identity verification and payouts. name: affiliate - description: >- Endpoints for the design partner program's customer surface: whether this workspace is a design partner, the badges its feedback has earned, and sending and reading that feedback. name: design-partner - description: >- Endpoints for the org-level AI business context (company description, ideal customer profile, buyer personas, interest signals and social proof), plus domain-based generation and the reference documents whose summaries ride alongside those fields. name: ai-context - description: >- Endpoints for the signed-in user's Google Drive connection: starting and finishing the OAuth grant, checking or dropping it, and minting the short-lived token the Google Picker needs. name: google-drive paths: /find-leads/tables/{table_id}/watch/stop/: post: tags: - find-leads summary: Stop a table's LinkedIn watch description: >- Stop the watch: it adds no one else and drops anyone waiting. The table and its rows stay, and it can be started again. operationId: stop_table_watch parameters: - in: path name: table_id required: true schema: format: uuid title: Table Id type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/LeadWatchSchema' description: Successful Response '401': content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' description: Unauthorized '403': content: application/json: schema: $ref: '#/components/schemas/ForbiddenResponse' description: Forbidden '404': content: application/json: schema: $ref: '#/components/schemas/NotFoundResponse' description: No LinkedIn watch feeds this table. '409': description: It already stopped. '422': content: application/json: schema: $ref: '#/components/schemas/UnprocessableEntityResponse' description: Invalid request made to the API. '500': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Internal server error. '502': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Bad gateway error. '503': content: application/json: schema: $ref: '#/components/schemas/ServerErrorResponse' description: Service unavailable. security: - APIKeyHeader: [] - HTTPBearer: [] components: schemas: LeadWatchSchema: description: 'A table''s LinkedIn watch: where it stands and what it may spend.' properties: ceiling_credits_per_day: description: >- The most one day can cost now: its people, plus every column that runs on a new person by itself. title: Ceiling Credits Per Day type: number credits_per_person: title: Credits Per Person type: number enrich_new_rows: title: Enrich New Rows type: boolean events: items: $ref: '#/components/schemas/LeadWatchEventSchema' title: Events type: array failure_filter: anyOf: - type: string - type: 'null' description: The filter a refused start was pinned to. title: Failure Filter failure_message: anyOf: - type: string - type: 'null' description: Why it could not start, in words to show. title: Failure Message funnel: anyOf: - $ref: '#/components/schemas/LeadWatchFunnelSchema' - type: 'null' id: format: uuid title: Id type: string last_person_at: anyOf: - format: date-time type: string - type: 'null' title: Last Person At notices: description: What to check about its filters, in our words. items: type: string title: Notices type: array pause_reason: anyOf: - $ref: '#/components/schemas/LeadWatchPauseReason' - type: 'null' description: >- Why it is paused: person, credits, limit (its total limit is spent), table_full, table_trashed, our_side (paused on our side), platform (paused for everyone) or landing_failed. credits, our_side and platform resume by themselves; the rest need a person. paused_at: anyOf: - format: date-time type: string - type: 'null' title: Paused At people_added: title: People Added type: integer people_per_day: title: People Per Day type: integer people_today: description: People added today (UTC). title: People Today type: integer people_waiting: description: >- People it was sent that wait to be added, held by a pause or the daily ceiling. title: People Waiting type: integer record_type: $ref: '#/components/schemas/LeadRecordType' spend_limit_credits: title: Spend Limit Credits type: number spent_credits: description: What it has charged for the people it added. title: Spent Credits type: number started_at: format: date-time title: Started At type: string status: $ref: '#/components/schemas/LeadWatchStatus' description: >- starting while it is being set up, active while it adds people, paused (see pause_reason), stopped by a person, or failed when it could not start. stopped_at: anyOf: - format: date-time type: string - type: 'null' title: Stopped At table_id: format: uuid title: Table Id type: string verified: description: Whether a test delivery proved people can reach this table. title: Verified type: boolean required: - id - table_id - record_type - status - people_per_day - credits_per_person - ceiling_credits_per_day - spend_limit_credits - spent_credits - enrich_new_rows - people_added - people_today - people_waiting - last_person_at - started_at - paused_at - stopped_at - verified - notices title: LeadWatchSchema type: object UnauthorizedResponse: properties: detail: description: The detail of why the request is unauthorized. title: Detail type: string required: - detail title: UnauthorizedResponse type: object ForbiddenResponse: properties: detail: description: The detail of why the request is forbidden. title: Detail type: string required: - detail title: ForbiddenResponse type: object NotFoundResponse: properties: detail: description: The detail of why the resource was not found. title: Detail type: string required: - detail title: NotFoundResponse type: object UnprocessableEntityResponse: properties: detail: description: >- The detail of the error. This is the error message to show to the user. You should also use the issues field to show more detailed error messages per field. Use this field for a single liner error message. title: Detail type: string issues: description: >- The issues that caused the error. There can be multiple issues. Each issue is a user-facing error message. items: $ref: '#/components/schemas/UnprocessableEntityIssue' title: Issues type: array required: - detail - issues title: UnprocessableEntityResponse type: object ServerErrorResponse: properties: detail: description: The detail of why the server returned an error. title: Detail type: string required: - detail title: ServerErrorResponse type: object LeadWatchEventSchema: description: One thing that happened to a watch. properties: actor_kind: description: user, api or system. title: Actor Kind type: string actor_name: anyOf: - type: string - type: 'null' description: The person or API key that did it; null for the system. title: Actor Name created_at: format: date-time title: Created At type: string detail: additionalProperties: true description: What changed, for example the reason of an automatic pause. title: Detail type: object event: $ref: '#/components/schemas/LeadWatchAuditEvent' required: - event - actor_kind - detail - created_at title: LeadWatchEventSchema type: object LeadWatchFunnelSchema: description: >- Why the watch added fewer people than it found, as last counted (at most an hour old). properties: added: description: People who got through. title: Added type: integer counted_at: format: date-time title: Counted At type: string found: description: People the watch found before any filter. title: Found type: integer rejected_by: additionalProperties: type: integer description: >- People each filter turned away, by filter name (roles, company_size, locations, industries, exclude_company_pages, duplicate, other). title: Rejected By type: object required: - found - rejected_by - added - counted_at title: LeadWatchFunnelSchema type: object LeadWatchPauseReason: description: |- Why a watch is paused, which decides who may resume it and how. Only ``person`` is a person's choice. ``credits``, ``our_side`` and ``platform`` lift by themselves once their cause clears, because the person never chose them. ``table_trashed`` lifts when a person restores the table. ``limit``, ``table_full`` and ``landing_failed`` wait for a person to fix the cause and resume. enum: - person - credits - limit - table_full - table_trashed - our_side - platform - landing_failed title: LeadWatchPauseReason type: string LeadRecordType: description: |- Which dataset a search runs against, and so which provider serves it. Values are persisted in String(16) columns, so every member must stay within 16 characters. enum: - people - companies - signal_companies - signal_people - lookalikes - local_businesses - hiring_companies - backlinks - post_engagers - profile_engagers - page_engagers - topic_mentions - event_attendees - search_results title: LeadRecordType type: string LeadWatchStatus: description: >- Where one LinkedIn watch stands. ``starting`` while it is being set up; ``active`` while it adds people; ``paused`` with a ``LeadWatchPauseReason``; ``stopped`` by a person (kept paused, so if it is started again it never sends anyone twice); ``failed`` when it could not start, with the reason stored. enum: - starting - active - paused - stopped - failed title: LeadWatchStatus type: string UnprocessableEntityIssue: properties: input: anyOf: - type: string - type: integer - type: number - type: boolean - items: {} type: array - additionalProperties: true type: object description: The user's input that caused the error. title: Input loc: description: >- The location of the error. Always contains 1 or 2 elements. The first element is the type of location (e.g. 'body', 'query', 'path', 'header'). The second element is the name of the field that caused the error. If the error is not related to a specific field, the second element is not present. items: type: string title: Loc type: array msg: description: The message of the error. The error message to show to the user. title: Msg type: string type: description: >- The type of the error. Useful for frontend code to handle different types of errors. title: Type type: string required: - loc - msg - type - input title: UnprocessableEntityIssue type: object LeadWatchAuditEvent: description: What happened to a watch, for its audit trail and the source panel. enum: - started - paused - resumed - stopped - restarted - settings_changed - filters_changed - auto_paused - auto_resumed - failed title: LeadWatchAuditEvent type: string securitySchemes: APIKeyHeader: in: header name: X-API-Key type: apiKey HTTPBearer: scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.