> ## 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. # Release one held contact into this sequence > ONE-1199: enrol a contact the workspace's cooldown or an exclusion list is holding back, ahead of its window. Applies to THIS sequence only — the contact stays held everywhere else and the clock is untouched. ## OpenAPI ````yaml /openapi.json post /sequences/{sequence_id}/contacts/{enrolment_id}/release/ 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 Getting started checklist: a workspace's progress through the six steps from its first people search to its first launched sequence. name: onboarding - description: Sender profiles, 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 rules: how long before anyone hears from us again, how many people at one account, and the reusable exclusion lists. name: contact_cooldown - description: 'Sequence authoring: the graph, the table-backed audience, previews.' name: sequences - 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 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: 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: >- The per-table AI Assistant: named conversations, the column suggestions a build turn produces, and the questions an analyze turn answers. name: table-assistant - 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}/release/: post: tags: - sequences summary: Release one held contact into this sequence description: >- ONE-1199: enrol a contact the workspace's cooldown or an exclusion list is holding back, ahead of its window. Applies to THIS sequence only — the contact stays held everywhere else and the clock is untouched. operationId: release_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 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. '409': description: This contact is not held. '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: EnrolmentReadSchema: properties: bounced: title: Bounced type: boolean company: anyOf: - type: string - type: 'null' title: Company company_key: anyOf: - type: string - type: 'null' title: Company Key created_at: format: date-time title: Created At type: string current_step_id: anyOf: - format: uuid type: string - type: 'null' title: Current Step Id display_name: anyOf: - type: string - type: 'null' title: Display Name due_at: anyOf: - format: date-time type: string - type: 'null' title: Due At email: anyOf: - type: string - type: 'null' title: Email excluded_list_id: anyOf: - format: uuid type: string - type: 'null' title: Excluded List Id hold_list_name: anyOf: - type: string - type: 'null' description: Which exclusion list excluded this contact. title: Hold List Name hold_reason: anyOf: - $ref: '#/components/schemas/HoldReason' - type: 'null' description: 'Which dial holds this contact: person or account.' hold_source_contacted_at: anyOf: - format: date-time type: string - type: 'null' description: >- The contact this hold is measured from. For an account hold this is a colleague's; the colleague is deliberately never named. title: Hold Source Contacted At hold_until: anyOf: - format: date-time type: string - type: 'null' description: When a held contact becomes eligible again. title: Hold Until id: format: uuid title: Id type: string linkedin_url: anyOf: - type: string - type: 'null' title: Linkedin Url 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' updated_at: format: date-time title: Updated At type: string 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 HoldReason: description: Which of the two workspace dials is holding a contact back (ONE-1199). enum: - person - account title: HoldReason 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. ONE-1199 adds two HELD states, which are neither live nor settled. COOLDOWN is a contact the workspace's recontact rule is holding back: it carries the eligible-again instant in ``due_at`` and resolves ITSELF at the first release sweep after that instant. It is deliberately outside ``uq_sequence_enrolment_one_live`` — a hold is not a live cadence, so two sequences may each hold the same person and each releases independently — and outside the due-queue's partial index, so the tick can never claim one. EXCLUDED is an exclusion-list match: the opposite fact, because there is no date on which it resolves. enum: - active - claimed - paused - completed - stopped - failed - suppressed - skipped_duplicate - cooldown - excluded title: EnrolmentStatus type: string StopReason: enum: - reply - unsubscribe - bounce - manual - company_reply - row_left_audience - step_removed - removed title: StopReason 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 ````