> ## 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. # Give a thumbs down > Say what is wrong with something an agent wrote. The agent learns a one-line learning from the reason (or rewrites the one about the same thing) and, where the output can be written again, writes it again with it. Sent again with the same `request_id`, it answers what the first one did. Only a signed-in person can, never an API key. ## OpenAPI ````yaml /openapi.json post /agent-learnings/thumbs-downs/ 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 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: >- 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/: post: tags: - agent-learnings summary: Give a thumbs down description: >- Say what is wrong with something an agent wrote. The agent learns a one-line learning from the reason (or rewrites the one about the same thing) and, where the output can be written again, writes it again with it. Sent again with the same `request_id`, it answers what the first one did. Only a signed-in person can, never an API key. operationId: create_thumbs_down requestBody: content: application/json: schema: $ref: '#/components/schemas/ThumbsDownCreateSchema' required: true responses: '201': content: application/json: schema: $ref: '#/components/schemas/ThumbsDownReadSchema' 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: What you rated no longer exists. '409': description: >- It can't be given here (the sentence says why), the agent keeps 30 learnings already, or its learnings changed meanwhile. '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: ThumbsDownCreateSchema: description: 'A thumbs down: what was wrong with something an agent wrote.' properties: reason: description: What is wrong, in the person's words. Required. maxLength: 1000 title: Reason type: string request_id: description: >- The client's key for this thumbs down: sent again (a double click, a retry), it answers what the first one did and writes nothing. format: uuid title: Request Id type: string subject: description: What it was given on. discriminator: mapping: agent_preview: '#/components/schemas/AgentPreviewSubjectSchema' reply_draft: '#/components/schemas/ReplyDraftSubjectSchema' sent_message: '#/components/schemas/SentMessageSubjectSchema' table_cells: '#/components/schemas/TableCellsSubjectSchema' task: '#/components/schemas/TaskSubjectSchema' writing_preview: '#/components/schemas/WritingPreviewSubjectSchema' propertyName: kind oneOf: - $ref: '#/components/schemas/TableCellsSubjectSchema' - $ref: '#/components/schemas/AgentPreviewSubjectSchema' - $ref: '#/components/schemas/TaskSubjectSchema' - $ref: '#/components/schemas/WritingPreviewSubjectSchema' - $ref: '#/components/schemas/ReplyDraftSubjectSchema' - $ref: '#/components/schemas/SentMessageSubjectSchema' title: Subject required: - reason - request_id - subject title: ThumbsDownCreateSchema type: object ThumbsDownReadSchema: description: What a thumbs down did. properties: action: $ref: '#/components/schemas/LearningAction' description: '`added` a learning, or `updated` one about the same thing.' agent_name: description: The agent that learned it. title: Agent Name type: string event_id: description: The thumbs down, for Undo. format: uuid title: Event Id type: string learning: anyOf: - $ref: '#/components/schemas/AgentLearningReadSchema' - type: 'null' description: >- The learning as written; null on a replay whose learning was deleted since. previous_text: anyOf: - type: string - type: 'null' description: What the updated learning said before; null for an added one. title: Previous Text redo: $ref: '#/components/schemas/RedoReadSchema' subject_key: description: >- What the thumbs down was given on, as `list_thumbs_downs` takes it, so a screen that gave it elsewhere (the AI Assistant's card) can follow its note. title: Subject Key type: string required: - event_id - action - learning - previous_text - agent_name - redo - subject_key title: ThumbsDownReadSchema 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 AgentPreviewSubjectSchema: description: One row of a table agent's Preview. properties: kind: const: agent_preview title: Kind type: string row_id: format: uuid title: Row Id type: string saved_agent_id: format: uuid title: Saved Agent Id type: string required: - kind - saved_agent_id - row_id title: AgentPreviewSubjectSchema type: object ReplyDraftSubjectSchema: description: A reply draft on the Inbox ribbon. properties: draft_id: format: uuid title: Draft Id type: string kind: const: reply_draft title: Kind type: string required: - kind - draft_id title: ReplyDraftSubjectSchema type: object SentMessageSubjectSchema: description: A message the agent wrote that went out. properties: kind: const: sent_message title: Kind type: string message_id: format: uuid title: Message Id type: string required: - kind - message_id title: SentMessageSubjectSchema type: object TableCellsSubjectSchema: description: Cells of one agent column. properties: column_id: format: uuid title: Column Id type: string kind: const: table_cells title: Kind type: string record_ids: items: format: uuid type: string maxItems: 50 minItems: 1 title: Record Ids type: array table_id: format: uuid title: Table Id type: string required: - kind - table_id - column_id - record_ids title: TableCellsSubjectSchema type: object TaskSubjectSchema: description: A task's card, and the message on it the person read. properties: kind: const: task title: Kind type: string outbound_message_id: format: uuid title: Outbound Message Id type: string task_id: format: uuid title: Task Id type: string required: - kind - task_id - outbound_message_id title: TaskSubjectSchema type: object WritingPreviewSubjectSchema: description: One contact of a sequence's AI writing Preview. properties: kind: const: writing_preview title: Kind type: string record_id: format: uuid title: Record Id type: string sequence_id: format: uuid title: Sequence Id type: string required: - kind - sequence_id - record_id title: WritingPreviewSubjectSchema type: object LearningAction: description: What one event did to an agent's learnings. enum: - added - updated - split - carried - skipped - seeded title: LearningAction type: string AgentLearningReadSchema: description: 'One learning: a one-line rule the agent follows on every output.' properties: batch_id: anyOf: - format: uuid type: string - type: 'null' description: >- The release that wrote it, for a learning split from a long prompt (`simplified`) or carried over from old feedback (`carried`): undoing that event (POST /agent-learnings/thumbs-downs/{event_id}/revert/ with this id) is Put back the original prompt. Null for a learning a thumbs down taught. title: Batch Id created_at: format: date-time title: Created At type: string created_by_user_id: anyOf: - type: string - type: 'null' description: Who taught it, or null for a release. title: Created By User Id id: format: uuid title: Id type: string last_event_id: anyOf: - format: uuid type: string - type: 'null' description: >- The latest thumbs down that wrote it, for Undo (POST /agent-learnings/thumbs-downs/{event_id}/revert/); null when none did or the learning was only read. title: Last Event Id source: $ref: '#/components/schemas/LearningSource' description: >- Where it was taught: the surface whose thumbs down added it, `simplified` when a long prompt was split into a goal and learnings, `carried` when old feedback was carried over. text: description: The rule, one line. title: Text type: string updated_at: format: date-time title: Updated At type: string required: - id - text - source - created_at - updated_at - created_by_user_id - last_event_id - batch_id title: AgentLearningReadSchema type: object RedoReadSchema: description: How the redo a thumbs down asked for went. properties: detail: anyOf: - type: string - type: 'null' description: Why it was refused, as the screen shows it. title: Detail state: $ref: '#/components/schemas/RedoState' description: >- `none` where nothing is redone (a sent message), `started` while it runs, `written` once the new output is there, `refused` when it could not run. required: - state - detail title: RedoReadSchema 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 LearningSource: description: >- Where a learning came from: the surface a thumbs down was given on, or a release pass. Also the ``surface`` of the event that wrote it. enum: - table_cells - agent_preview - task - writing_preview - reply_draft - sent_message - simplified - carried - template title: LearningSource type: string RedoState: description: How the redo a thumbs down asked for went. enum: - none - started - written - refused title: RedoState 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.