> ## 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. # Read one activity row > One row of Activity, exactly as the list reads it: what went out (or was refused), as which sender, how it ended and who let it go. A link to one row opens it with this, whichever page of the list it sits on. ## OpenAPI ````yaml /openapi.json get /outreach-tasks/activity/{activity_id}/ 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 spend 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 listing, checking and deleting integrations. name: integrations - description: >- Create, preview and update an integration of any type: the body's integration_type picks the config and credentials it takes. name: integration-specific - 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: >- AI apps connected to the workspace: Claude, ChatGPT, Claude Code or any other MCP client a person signed in to Oneprofile's MCP server with. name: ai_apps - description: Endpoints for managing billing and subscription information. name: billing - description: >- Accounts: every company the workspace's tables name, with the people at it, its key facts, its tables, its org chart and what went to its people; the tables that feed it (Sources) and the merges a person made. name: accounts - 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 an agent's Preview: example rows run one at a time, and a Looks good on each. Needs work lives under agent-learnings. name: agent-training - description: >- An agent's learnings, the one-line rules it follows on every output, and the thumbs down that teaches them: give one with what was wrong, list the ones on a subject, Undo one, and price the redo it would run. name: agent-learnings - 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 recording where a new workspace came from: the marketing page or campaign its signup link carried, sent once after signup. name: attribution - 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: /outreach-tasks/activity/{activity_id}/: get: tags: - outreach summary: Read one activity row description: >- One row of Activity, exactly as the list reads it: what went out (or was refused), as which sender, how it ended and who let it go. A link to one row opens it with this, whichever page of the list it sits on. operationId: get_outreach_activity parameters: - in: path name: activity_id required: true schema: format: uuid title: Activity Id type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/OutreachActivityReadSchema' 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: Activity 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: OutreachActivityReadSchema: description: >- One email or LinkedIn step that went out as a sender, or a task a person refused. properties: acted_at: anyOf: - format: date-time type: string - type: 'null' description: >- When a LinkedIn step acted on LinkedIn. Set on a step marked failed means it went through after all, after it was marked failed. title: Acted At agent_written: description: Whether the outbound agent wrote the words. title: Agent Written type: boolean ask_reason: anyOf: - $ref: '#/components/schemas/AskReason' - type: 'null' description: >- Why it was held for a person before it went; null when it was not held. audience_table_id: anyOf: - format: uuid type: string - type: 'null' description: >- The table the sequence reads its audience from, for opening the contact's row; null outside a sequence or when the sequence is gone. title: Audience Table Id background: description: >- Whether this is one of our own LinkedIn reads of the sender's account (the inbox, the sent connection requests, the newest connections, one conversation), which acts on nobody. title: Background type: boolean body: anyOf: - type: string - type: 'null' description: >- The words as they went out, or would have for a refusal; for a Browser use run, the site it worked on. title: Body channel: $ref: '#/components/schemas/TaskChannel' contact_company: anyOf: - type: string - type: 'null' description: The contact's company, from their audience row. title: Contact Company contact_identity: anyOf: - type: string - type: 'null' description: The address or LinkedIn profile behind the label. title: Contact Identity contact_label: description: >- The contact as the queue names them: a name, else an address or profile. title: Contact Label type: string contact_title: anyOf: - type: string - type: 'null' description: The contact's job title, from their audience row. title: Contact Title decided_at: anyOf: - format: date-time type: string - type: 'null' title: Decided At decided_by_display_name: anyOf: - type: string - type: 'null' description: >- Who approved it, refused it or sent it: a person's name, an API key's, or the platform's. Null when nobody did. title: Decided By Display Name decision: $ref: '#/components/schemas/ActivityDecision' detail: anyOf: - type: string - type: 'null' description: >- Why it failed, in the channel's words, or why the person refused it; for a Browser use run, why it needed a person or failed. title: Detail enrolment_id: anyOf: - format: uuid type: string - type: 'null' description: >- The contact's place in the sequence, for opening them on its Audience tab. title: Enrolment Id error_code: anyOf: - type: string - type: 'null' description: >- The LinkedIn step's error code, or for a skip its specific reason, for the words every LinkedIn surface gives it. title: Error Code found_already: default: false description: >- A step that was cut off, came back, and found its own earlier attempt had already done it. title: Found Already type: boolean hand_edited: description: >- A person edited the agent's words before they went, so Needs work is refused on them. title: Hand Edited type: boolean id: format: uuid title: Id type: string kind: description: >- The LinkedIn action slug, or `email` (a sequence's email), `reply`, or `browser_use` (a settled Browser use run, on the `browser` channel). title: Kind type: string linkedin_action_id: anyOf: - format: uuid type: string - type: 'null' title: Linkedin Action Id looks_good: description: >- A person marked the words that went out Looks good (PUT /agent-learnings/sent-messages/{message_id}/looks-good/). title: Looks Good type: boolean mailbox_address: anyOf: - type: string - type: 'null' description: The address an email left from; null for LinkedIn. title: Mailbox Address mailbox_id: anyOf: - format: uuid type: string - type: 'null' title: Mailbox Id occurred_at: description: >- When it was sent, when the LinkedIn step ended, or when it was refused. format: date-time title: Occurred At type: string outbound_message_id: anyOf: - format: uuid type: string - type: 'null' description: >- The outbound agent's message whose words went out (or would have, for a refusal): a sequence's email or LinkedIn step, a connection request's note, an approved reply. A thumbs down on what went out is given on it (`message:`), whether or not it had a task. Null when the agent wrote none of the words, and on rows from before it was kept that nothing could fill. title: Outbound Message Id outcome: $ref: '#/components/schemas/ActivityOutcome' proposed_learning_event_id: anyOf: - format: uuid type: string - type: 'null' description: >- The feedback session waiting on the words that went out (`outbound_message_id`): notes were given (`message:`) and what they would teach waits for Looks good, which saves it, or Discard feedback, which drops it. The row's 'Unfinished feedback' chip. Read it with GET /agent-learnings/thumbs-downs/{event_id}/. Null when none waits. title: Proposed Learning Event Id record_id: anyOf: - format: uuid type: string - type: 'null' description: The contact's row in the sequence's audience table. title: Record Id sender_profile_id: format: uuid title: Sender Profile Id type: string sender_profile_name: anyOf: - type: string - type: 'null' description: The sender it went out as; null when the sender was since deleted. title: Sender Profile Name sent_without_note: default: false description: >- A connection request LinkedIn sent the moment Connect was pressed, before its note could be added: the connection request went, the note did not. title: Sent Without Note type: boolean sequence_id: anyOf: - format: uuid type: string - type: 'null' title: Sequence Id sequence_name: anyOf: - type: string - type: 'null' title: Sequence Name step_id: anyOf: - format: uuid type: string - type: 'null' title: Step Id step_name: anyOf: - type: string - type: 'null' description: >- The step as its card in the Builder names it; null outside a sequence. title: Step Name step_position: anyOf: - type: integer - type: 'null' title: Step Position subject: anyOf: - type: string - type: 'null' description: >- An email's subject line; for a Browser use run, the outcome it settled on (null for Needs human and a failure). title: Subject task_id: anyOf: - format: uuid type: string - type: 'null' description: Its task on the Tasks page, when it had one. title: Task Id thread_id: anyOf: - format: uuid type: string - type: 'null' description: The inbox conversation, when there is one. title: Thread Id required: - id - sender_profile_id - sender_profile_name - channel - kind - background - occurred_at - outcome - decision - decided_by_display_name - decided_at - ask_reason - agent_written - contact_label - contact_identity - sequence_id - sequence_name - step_id - step_name - step_position - enrolment_id - record_id - audience_table_id - task_id - linkedin_action_id - mailbox_id - mailbox_address - thread_id - outbound_message_id - subject - body - detail - error_code - looks_good - hand_edited title: OutreachActivityReadSchema 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 AskReason: description: >- Why a message that could have sent unattended was put in front of a person. One vocabulary for every gate between an agent writing a message and the message leaving: what the agent itself said about the draft (``LOW_CONFIDENCE``, ``FINDINGS``, ``INSUFFICIENT_DATA``, ``POLICY``), what the sender or the cadence asked for (``ALWAYS_ASK``, ``SEQUENCE_MANUAL``, ``STEP_REQUIRES_APPROVAL``), what the pacing rules refused (``DAILY_CAP``, ``CONSECUTIVE_CAP``, ``THREAD_CAP``, ``HOURLY_CAP``, ``ORG_DAILY_CAP``), what the mailbox or the thread made unsafe (``UNVERIFIED_SENDER``, ``DIFFERENT_SENDER``, ``LABEL``, ``QUESTION``, ``STALE_INBOUND``, ``SEQUENCE_GONE``), and what the counterparty turned out to be (``BOT_QUESTION``, ``AUTOMATED_COUNTERPARTY``, ``AUTHENTICATION``, ``LANGUAGE``, ``LINKEDIN_ONLY``). ``KILL_SWITCH`` is the platform switch that stops unattended sending outright, and ``SEND_INTERRUPTED`` an unattended reply whose send never got as far as a provider. ``SENDER_SWITCHED_TO_MANUAL`` is a LinkedIn step queued unasked that went back to a person because its sender switched to manual before it ran. Stored on the task so the queue can say why each row is there, and so "why did nothing send" is answerable by counting rows rather than by reading logs. enum: - low_confidence - findings - insufficient_data - policy - always_ask - sequence_manual - step_requires_approval - daily_cap - unverified_sender - suppressed - different_sender - label - question - consecutive_cap - thread_cap - hourly_cap - org_daily_cap - stale_inbound - sequence_gone - bot_question - automated_counterparty - kill_switch - authentication - language - linkedin_only - send_interrupted - sender_switched_to_manual title: AskReason type: string TaskChannel: description: >- Which channel performs the task once it is allowed to run. ``BROWSER`` is the one channel that performs nothing: a Browser use run that settled on Needs human leaves a task for a person to pick up what the agent could not do (BU-08). Its contact already went on down the Needs human arm, so the task is a to-do with one verb, done, and no approval or rejection reaches it. enum: - linkedin - email - browser title: TaskChannel type: string ActivityDecision: description: >- Who let one unit of outreach go, or refused it. ``APPROVED``: a person (or an API key) approved it before it went. ``AUTOMATIC``: nobody was asked; the sender's or the sequence's rules let it go. ``REJECTED``: a person refused it, so it never went. ``SENT_BY_PERSON``: a person wrote it and sent it themselves, from the inbox. ``NOT_RECORDED``: a LinkedIn step that ran before Activity existed whose approval a later step of the same contact has since overwritten; saying so is truer than guessing. enum: - approved - automatic - rejected - sent_by_person - not_recorded title: ActivityDecision type: string ActivityOutcome: description: >- How one unit of outreach ended. ``SENT`` is an email the provider accepted, or a LinkedIn message, InMail or connection request that went out, so one thing reads one way on both channels (2026-10-21); ``DONE`` a LinkedIn step that only acted on a profile (a view, a follow, a like, a withdrawal). ``SKIPPED`` is a step that did not apply or was passed over in the extension; ``ALREADY_PENDING`` the one skip every LinkedIn surface names apart, a connection request somebody had already sent; ``STOPPED`` one stopped while a browser ran it. ``NOT_SENT`` is a task a person refused, which never reached its channel. ``RECEIVED`` is the one row that is not ours: a message the contact sent us, or their acceptance of our connection request (``ReceivedActivityKind``, review AC-11). A Browser use run (BU-18) settles ``DONE`` on one of its step's outcomes, ``NEEDS_HUMAN`` when it left the contact for a person, or ``FAILED``. enum: - sent - done - failed - skipped - already_pending - stopped - not_sent - received - needs_human title: ActivityOutcome 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.