> ## 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. # Get a thumbs down > One thumbs down by its id, as the list on its subject shows it: the learning it wrote or proposes, and how its redo and any Undo went. ## OpenAPI ````yaml /openapi.json get /agent-learnings/thumbs-downs/{event_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: 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: /agent-learnings/thumbs-downs/{event_id}/: get: tags: - agent-learnings summary: Get a thumbs down description: >- One thumbs down by its id, as the list on its subject shows it: the learning it wrote or proposes, and how its redo and any Undo went. operationId: get_thumbs_down parameters: - in: path name: event_id required: true schema: format: uuid title: Event Id type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/ThumbsDownEventReadSchema' 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: Thumbs down 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: ThumbsDownEventReadSchema: description: One thumbs down, as the note in place shows it. properties: action: $ref: '#/components/schemas/LearningAction' agent_name: title: Agent Name type: string created_at: format: date-time title: Created At type: string id: format: uuid title: Id type: string proposal: anyOf: - $ref: '#/components/schemas/ProposalReadSchema' - type: 'null' description: >- The learning an outbound thumbs down proposed; null for a table agent's. record_ids: description: >- The rows a thumbs down on cells covered, so the grid shows its note on each; empty on every other surface. items: format: uuid type: string title: Record Ids type: array redo_detail: anyOf: - type: string - type: 'null' title: Redo Detail redo_state: $ref: '#/components/schemas/RedoState' restore: $ref: '#/components/schemas/RestoreState' description: >- Where putting the original output back stands after Undo: `none`, `waiting`, `restored` or `left`. restore_detail: anyOf: - type: string - type: 'null' description: Why the original was left as the redo left it. title: Restore Detail saved_agent_id: anyOf: - format: uuid type: string - type: 'null' description: >- The saved agent the thumbs down was given to (for an outbound one, its sequence's writer, whose learnings a full list's "replace one" picks from); null for an unlinked column's. title: Saved Agent Id status: $ref: '#/components/schemas/LearningEventStatus' description: >- `applied` (its learning is saved), `undone` after Undo, `proposed` while an outbound thumbs down's learning waits for a person (Will learn), `dismissed` once that one was thrown away (Undo, a rejection, a discard, or a week unsaved). subject_key: description: >- What it was given on, as `subject_key` names it: a read of several subjects at once sorts its thumbs downs back to each by this. title: Subject Key type: string text_after: anyOf: - type: string - type: 'null' description: The learning as the thumbs down wrote it. title: Text After text_before: anyOf: - type: string - type: 'null' description: What an updated learning said before. title: Text Before would_have_written: anyOf: - $ref: '#/components/schemas/WouldHaveWrittenReadSchema' - type: 'null' description: >- On a sent message: what the agent would have sent instead, once written (`redo_state` `written`); null before then and on every other surface. required: - id - subject_key - action - text_after - text_before - status - restore - restore_detail - redo_state - redo_detail - created_at - agent_name title: ThumbsDownEventReadSchema 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 LearningAction: description: What one event did to an agent's learnings. enum: - added - updated - split - carried - skipped - seeded title: LearningAction type: string ProposalReadSchema: description: >- The learning an outbound thumbs down proposes, before a person saves it (Will learn). Saved by Save (POST .../save/), by approving the rewritten task or reply, or by Looks good on the rewritten Preview contact; thrown away by Undo, a rejection or a discard. properties: auto_rewrites: description: >- How many messages waiting for approval were written again once it was saved. title: Auto Rewrites type: integer moved_from_text: anyOf: - type: string - type: 'null' description: >- Once saved for every sequence: this sequence's learning it took the place of, which Undo puts back. title: Moved From Text replaces_scope: anyOf: - $ref: '#/components/schemas/ProposedScope' - type: 'null' description: >- Whose learning it rewrites: this sequence's, or every sequence's. A rewrite of every sequence's learning kept at `sequence` scope saves a new learning for this sequence instead (Replaces in this sequence). replaces_text: anyOf: - type: string - type: 'null' description: >- The saved learning it rewrites, as it read when proposed (Replaces: ...); null when it adds one. title: Replaces Text saved_learning_id: anyOf: - format: uuid type: string - type: 'null' description: >- The learning it saved, once saved; null while it waits or once thrown away. title: Saved Learning Id scope: $ref: '#/components/schemas/ProposedScope' description: >- `sequence`: this sequence only (the default). `account`: every sequence's writer, its emails, LinkedIn messages and replies. text: description: The learning as it would be saved, one line. title: Text type: string required: - text - scope - replaces_text - replaces_scope - saved_learning_id - moved_from_text - auto_rewrites title: ProposalReadSchema type: object RedoState: description: How the redo a thumbs down asked for went. enum: - none - started - written - refused title: RedoState type: string RestoreState: description: Where putting an undone event's original output back stands. enum: - none - waiting - restored - left title: RestoreState type: string LearningEventStatus: description: >- Where an event stands. An outbound thumbs down starts ``proposed``: the learner's learning waits on the rewritten message until a person saves it (``applied``) or it is thrown away (``dismissed``). A table agent's thumbs down is ``applied`` at once, as before. enum: - applied - undone - proposed - dismissed title: LearningEventStatus type: string WouldHaveWrittenReadSchema: description: >- What the agent would have sent in place of a sent message, with the proposed learning. properties: body: description: The words. title: Body type: string subject: anyOf: - type: string - type: 'null' description: The subject line; null for LinkedIn. title: Subject required: - subject - body title: WouldHaveWrittenReadSchema 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 ProposedScope: description: Which writers a proposed learning reaches once saved. enum: - sequence - account title: ProposedScope 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.