> ## 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. # Move one contact to another sequence > Move to another sequence, all or nothing: the contact leaves this sequence only when the target takes them. When the target cannot (no address it can use, the do-not-contact list, the recontact rule, already in it, a different audience table) the answer is a 422 whose message says why, and the contact stays here untouched. Returns the contact's place in THIS sequence, now stopped. ## OpenAPI ````yaml /openapi.json post /sequences/{sequence_id}/contacts/{enrolment_id}/move/ 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}/contacts/{enrolment_id}/move/: post: tags: - sequences summary: Move one contact to another sequence description: >- Move to another sequence, all or nothing: the contact leaves this sequence only when the target takes them. When the target cannot (no address it can use, the do-not-contact list, the recontact rule, already in it, a different audience table) the answer is a 422 whose message says why, and the contact stays here untouched. Returns the contact's place in THIS sequence, now stopped. operationId: move_enrolment parameters: - in: path name: sequence_id required: true schema: format: uuid title: Sequence Id type: string - in: path name: enrolment_id required: true schema: format: uuid title: Enrolment Id type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/MoveContactRequestSchema' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/EnrolmentReadSchema' 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: The target sequence would not take the contact; they stay here. '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: MoveContactRequestSchema: description: Where Move to another sequence should put the contact. properties: target_sequence_id: description: The sequence to move the contact to. It must send to the same table. format: uuid title: Target Sequence Id type: string required: - target_sequence_id title: MoveContactRequestSchema type: object EnrolmentReadSchema: properties: bounced: title: Bounced type: boolean company_key: anyOf: - type: string - type: 'null' title: Company Key contact_company: anyOf: - type: string - type: 'null' description: Their company, from whichever column of the audience row holds one. title: Contact Company contact_name: anyOf: - type: string - type: 'null' description: >- The person's name from their audience row: a full-name column where filled, else the given and family names joined. Null when the table names nobody. title: Contact Name contact_number: default: 0 description: >- This contact's ordinal within the sequence, from 1. A label of last resort, for a contact with neither an address nor a LinkedIn profile. title: Contact Number type: integer contact_title: anyOf: - type: string - type: 'null' description: >- Their job title, from whichever column of the audience row holds one. title: Contact Title created_at: format: date-time title: Created At type: string current_step_id: anyOf: - format: uuid type: string - type: 'null' title: Current Step Id decides_at: anyOf: - format: date-time type: string - type: 'null' description: >- For a contact on a condition that waits (Replied?, Bounced?, Accepted?): when the branch is decided. In the past on an acceptance, the window is over and the verdict waits for the sender's browser to look at the sent invitations again. title: Decides At due_at: anyOf: - format: date-time type: string - type: 'null' title: Due At email: anyOf: - type: string - type: 'null' title: Email failure_reason: anyOf: - type: string - type: 'null' description: >- Why a failed contact stopped, in the words of its status cell: for a LinkedIn step, the browser's own reason. Retry runs the same step again. Null on every other status. title: Failure Reason held_by_sequence: anyOf: - $ref: '#/components/schemas/HeldBySequenceReadSchema' - type: 'null' description: >- On a contact skipped because they are in another live sequence (status skipped_duplicate): that sequence of this workspace, by id and name. Null for every other status, and once nothing holds the contact, which is when the next sync takes them in. hold_reason: anyOf: - $ref: '#/components/schemas/HoldReason' - type: 'null' description: >- Why the send path pushed this contact's next attempt out to due_at. Set only on an active contact whose due_at is still ahead. 'window' also covers a contact due on one of the sending window's openings, whoever scheduled them. id: format: uuid title: Id type: string last_contacted_at: anyOf: - format: date-time type: string - type: 'null' description: >- The touch a cooldown stop is measured from. Whoever made it is deliberately never named — it may be a colleague's sequence entirely. title: Last Contacted At last_step_at: anyOf: - format: date-time type: string - type: 'null' description: When that step ran. title: Last Step At last_step_id: anyOf: - format: uuid type: string - type: 'null' description: >- The step this contact last actually ran. Not the step before current_step_id: on a branching graph those are different steps. title: Last Step Id linkedin_queue: anyOf: - $ref: '#/components/schemas/LinkedInQueueState' - type: 'null' description: >- Set beside waiting_on 'linkedin': where the contact's step stands in the sending account's line. 'running' is in a browser now; 'queued' is in line (see linkedin_steps_ahead and linkedin_starts_at); the rest say why the line is not moving for it: a daily or weekly limit for its kind, no browser checked in for fifteen minutes, LinkedIn asking to verify the account, or the account disconnected. linkedin_resets_at: anyOf: - format: date-time type: string - type: 'null' description: >- For a step held by a daily or weekly limit, when the limit it waits on resets (a UTC midnight). Null otherwise. title: Linkedin Resets At linkedin_starts_at: anyOf: - format: date-time type: string - type: 'null' description: >- When the step is expected to start, simulated the way the account's governor hands steps out: the next gap is exact, later gaps are the account's time between steps widened by the average jitter, and a step held by a daily or weekly limit starts after that limit resets. Null where no time can be named. title: Linkedin Starts At linkedin_steps_ahead: anyOf: - type: integer - type: 'null' description: For a queued step, how many of the account's steps run before it. title: Linkedin Steps Ahead linkedin_url: anyOf: - type: string - type: 'null' title: Linkedin Url mailbox_address: anyOf: - type: string - type: 'null' description: >- The address this contact is emailed from. A contact is only ever emailed from the mailbox that first emailed them, in any sequence. Null until something has emailed them. title: Mailbox Address mailbox_issue: anyOf: - $ref: '#/components/schemas/MailboxIssue' - type: 'null' description: >- Why that mailbox cannot send for this sequence, set while it is what stops the contact (stop_reason mailbox_removed: deleted, not_on_sequence) or holds them (hold_reason mailbox_waiting: disconnected, no_sender). reachable: default: true description: >- Whether any channel this sequence's steps use can reach the contact: an email address for an email step, a LinkedIn profile URL for a LinkedIn one. A sequence with no sending step yet counts both. title: Reachable type: boolean record_id: format: uuid title: Record Id type: string replied_at: anyOf: - format: date-time type: string - type: 'null' title: Replied At status: $ref: '#/components/schemas/EnrolmentStatus' stop_reason: anyOf: - $ref: '#/components/schemas/StopReason' - type: 'null' unreachable_reason: anyOf: - $ref: '#/components/schemas/UnreachableReason' - type: 'null' description: >- Which address the contact lacks, set only while being unreachable is what holds them: the Contacts tab reads it as Unreachable, and the audience eligibility counts them under missing_contact_details. Null for a reachable contact and for one who is settled or held by something named first (do not contact, another sequence, a cooldown). updated_at: format: date-time title: Updated At type: string waiting_on: anyOf: - $ref: '#/components/schemas/WaitingOn' - type: 'null' description: >- What the approval queue holds this contact behind, read from the task for their current step: a person's approval, a LinkedIn browser, or an approved email the engine has not sent yet. Null when nothing does. required: - id - record_id - email - status - current_step_id - due_at - stop_reason - bounced - replied_at - company_key - created_at - updated_at title: EnrolmentReadSchema 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 HeldBySequenceReadSchema: description: The live sequence a skipped contact is in. properties: id: format: uuid title: Id type: string name: title: Name type: string required: - id - name title: HeldBySequenceReadSchema type: object HoldReason: description: >- Why the send path pushed a live contact's ``due_at`` out instead of sending. Stored beside the date it explains so the Contacts tab can say "Approved, window opens in 3 hours" rather than a bare date. Only ever meaningful on an ACTIVE row whose date is still ahead; any other write clears it. enum: - window - daily_cap - no_mailbox - pacing - agent_unavailable - no_message - agent_writing - mailbox_waiting - no_linkedin_account title: HoldReason type: string LinkedInQueueState: description: >- Where one step stands in its account's line, for the people waiting on it. ``RUNNING`` is in a browser now. ``QUEUED`` is in line, with how many are ahead of it and when it is expected to start. The rest say why the line is not moving for it: a daily or weekly limit reached for its kind, a limit set to zero (``KIND_DISABLED``, which no reset lifts), no browser checked in for longer than ``offline_warning_seconds``, LinkedIn asking the member to verify the account (a checkpoint), or the account disconnected. Not "paused", which is already what a sequence is when a person stops it. The last two were one "account blocked" state. They are two because the fix is different and the words have to say which: a checkpoint is cleared in the connected Chrome, a disconnect by connecting again. enum: - running - queued - daily_limit - weekly_limit - kind_disabled - browser_offline - verify_account - disconnected title: LinkedInQueueState type: string MailboxIssue: description: >- Why the mailbox a contact is emailed from cannot send for them right now. Read at the time, never stored. The first two stop the contact, because nothing on its own brings the address back to this sequence; the last two make them wait, because a reconnect or a sender does. enum: - deleted - not_on_sequence - disconnected - no_sender title: MailboxIssue type: string EnrolmentStatus: description: >- Where one contact stands in one sequence. ACTIVE rows carry a ``due_at`` and are what the tick claims; CLAIMED is the in-flight guard between claim and outcome. PAUSED (SEQ-30) is a deliberate per-contact hold: unclaimable because the tick claims strictly on ACTIVE, yet still LIVE — it keeps its step and its one-live-sequence slot, and a compliance stop (reply, unsubscribe) reaches it. Everything else is settled: COMPLETED walked off the end; STOPPED was halted (reply, unsubscribe, bounce, manual, company pause); FAILED is terminal per the phase-1 ruling; SUPPRESSED was on the do-not-contact list; SKIPPED_DUPLICATE lost the one-live-sequence-per-contact rule, with the reason visible in the grid. A contact the workspace's recontact rule refuses is STOPPED with ``StopReason.COOLDOWN``. There is deliberately no held state: a cooldown settles a contact rather than parking them, so nothing here waits on a date and nothing lets itself out later. AWAITING_ACTION (F-25) is a contact parked behind a task that needs a person or a channel, modelled on PAUSED: live, keeps its step and its one-live-sequence slot, unclaimable because the tick claims strictly on ACTIVE, and a compliance stop reaches it. Unlike PAUSED nobody wakes it by hand — only the outreach-task sweep does, once the task it waits on is decided or delivered. Deliberately not "awaiting approval": an AUTO-mode LinkedIn park is waiting for a browser rather than for anyone's approval, and this value is the word the Contacts tab shows for both. PENDING is a draft's roster: in, standing on a step, and NOT live. Binding an audience enrols on the spot so the Contacts tab can show who is in, but a sequence nobody has launched must not hold anybody's one-live-sequence slot, or a second sequence written for the same people skips them all. ``uq_sequence_enrolment_one_live`` leaves PENDING out, the tick never claims it, and launch turns each row ACTIVE, settling the ones another sequence took meanwhile as SKIPPED_DUPLICATE. enum: - pending - active - claimed - paused - awaiting_action - completed - stopped - failed - suppressed - skipped_duplicate title: EnrolmentStatus type: string StopReason: enum: - reply - unsubscribe - bounce - manual - company_reply - row_left_audience - step_removed - removed - cooldown - rejected - mailbox_removed title: StopReason type: string UnreachableReason: description: >- Which address a contact lacks for the channels their sequence uses. Derived at read time from the contact's row and the graph, never stored. Named by channel rather than as one "missing contact details", because the fix is different: an email-only cadence needs an address, a LinkedIn-only one a profile URL. enum: - no_email - no_linkedin_url - no_email_or_linkedin_url title: UnreachableReason type: string WaitingOn: description: >- What a live contact is held behind in the approval queue, read at list time. Derived from the contact's task for its current step, never stored: the task is the truth, and a copy on the enrolment would lag behind it. enum: - approval - linkedin - send title: WaitingOn 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 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.