> ## 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. # Why nothing is moving > Whether anybody on the sequence can move right now, and if not, why: every reason holding live contacts, worst first, with how many each holds and, for a LinkedIn reason, whose account it is. The Overview headline, the Audience banner, the header caption and each step card read this one answer. ## OpenAPI ````yaml /openapi.json get /sequences/{sequence_id}/holds/ 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: /sequences/{sequence_id}/holds/: get: tags: - sequences summary: Why nothing is moving description: >- Whether anybody on the sequence can move right now, and if not, why: every reason holding live contacts, worst first, with how many each holds and, for a LinkedIn reason, whose account it is. The Overview headline, the Audience banner, the header caption and each step card read this one answer. operationId: get_sequence_holds parameters: - in: path name: sequence_id required: true schema: format: uuid title: Sequence Id type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/SequenceHoldsReadSchema' 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: Not found. '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: SequenceHoldsReadSchema: description: Whether anybody on a sequence can move right now, and if not, why. properties: holds: items: $ref: '#/components/schemas/SequenceHoldReadSchema' title: Holds type: array moving: description: >- Live contacts nothing holds: due now, sending, in line on a working browser, or waiting out an ordinary step delay. Zero with holds listed means nobody can move. title: Moving type: integer steps: items: $ref: '#/components/schemas/StepHoldReadSchema' title: Steps type: array window_opens_at: anyOf: - format: date-time type: string - type: 'null' description: The sending window's next opening while it is shut; null while open. title: Window Opens At required: - moving - window_opens_at - holds - steps title: SequenceHoldsReadSchema 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 SequenceHoldReadSchema: description: >- How many live contacts one reason holds, and what a page needs to say it. properties: action_kind: anyOf: - type: string - type: 'null' description: 'For a LinkedIn limit: the kind of step it stopped.' title: Action Kind contacts: title: Contacts type: integer last_seen_at: anyOf: - format: date-time type: string - type: 'null' description: 'For an offline browser: its last check-in.' title: Last Seen At limit: anyOf: - type: integer - type: 'null' description: 'For a LinkedIn limit: the limit.' title: Limit long_offline: default: false description: 'For an offline browser: nothing for over a day.' title: Long Offline type: boolean reason: $ref: '#/components/schemas/SequenceHold' description: >- What holds them, worst first in the list: a LinkedIn account asking to be verified or disconnected, no mailbox, a step with no message, an offline LinkedIn browser, approval, the email or LinkedIn daily limit, the weekly invitation limit, the sending window, or the AI writer. sender_name: anyOf: - type: string - type: 'null' description: That sender's first name, else their name. title: Sender Name sender_profile_id: anyOf: - format: uuid type: string - type: 'null' description: 'For a LinkedIn reason: the sender whose account it is.' title: Sender Profile Id until: anyOf: - format: date-time type: string - type: 'null' description: >- When the reason ends on its own: the window's next opening, a daily limit's reset, the AI writer's next try. Null where only a person ends it. title: Until used: anyOf: - type: integer - type: 'null' description: 'For a LinkedIn limit: how many used.' title: Used required: - reason - contacts title: SequenceHoldReadSchema type: object StepHoldReadSchema: description: The worst reason holding contacts on one step, for the step's card. properties: contacts: title: Contacts type: integer reason: $ref: '#/components/schemas/SequenceHold' step_id: format: uuid title: Step Id type: string required: - step_id - reason - contacts title: StepHoldReadSchema type: object 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 SequenceHold: description: >- One reason a live contact cannot move right now, as the sequence's pages say it. The stored ``HoldReason`` and the task-derived ``WaitingOn`` each cover part of this; the LinkedIn account's own state covers the rest. This is their union, read at request time, so the Overview, the Audience tab, the header and the Sequences list name one reason with one word (the silent-stall plan, approved 2026-09-30). Listed worst first: the order is the order a page picks its one headline or banner by. The first five need a person; ``APPROVAL`` does too but has its own row and banner already; the rest end on their own. enum: - linkedin_verify_account - linkedin_disconnected - no_mailbox - no_message - linkedin_browser_offline - approval - daily_cap - linkedin_daily_limit - linkedin_weekly_limit - window - writing_delayed title: SequenceHold 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.