> ## 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. # Reject a proposed action > Decline a proposal. Nothing runs, and the card records who said no. With `dry_run`, answers the card as declining it would leave it and changes nothing. ## OpenAPI ````yaml /openapi.json post /assistant/actions/{proposal_id}/reject/ 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: /assistant/actions/{proposal_id}/reject/: post: tags: - workspace-actions summary: Reject a proposed action description: >- Decline a proposal. Nothing runs, and the card records who said no. With `dry_run`, answers the card as declining it would leave it and changes nothing. operationId: reject_workspace_action parameters: - in: path name: proposal_id required: true schema: format: uuid title: Proposal Id type: string - description: Report what would happen, and change nothing. in: query name: dry_run required: false schema: default: false description: Report what would happen, and change nothing. title: Dry Run type: boolean responses: '200': content: application/json: schema: $ref: '#/components/schemas/ActionProposalReadSchema' 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: Proposal not found. '409': content: application/json: schema: $ref: '#/components/schemas/ActionConflictResponseSchema' description: The proposal is not in a state this decision applies to. '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: ActionProposalReadSchema: description: >- One action the assistant proposed or applied, and what became of it: the card. Prices are quoted in credits, never tenths, and never as a raw id: who decided is a display name resolved at this boundary. ``applied_result`` is the verb's own record of what it made (the new column's id, the rows enrolled), which is what the card links to. properties: applied_result: anyOf: - additionalProperties: true type: object - type: 'null' description: >- The verb's or tool's own record of what it made; null until applied. A tool card carries `content` (what the assistant read back), `link` (an app path to the thing), `link_label` (its name), `entity_id`, `opens` (whether the page should go to the link when this lands) and `made` (what was created, for the AI-made mark), plus any facts the tool added. title: Applied Result approve_label: description: >- What the Approve button says: "Approve", or with the most it spends, "Approve · up to 8 credits", or with a flat price, "Approve · 8 credits", or per day, "Approve · up to 145 credits a day". title: Approve Label type: string batch_id: anyOf: - format: uuid type: string - type: 'null' description: >- Cards the assistant raised together in one reply share this, so they can be shown and approved as a group. Null for a card raised on its own. title: Batch Id charged_credits: anyOf: - type: number - type: 'null' description: >- What the run this card started was charged, in credits, once it finished. Null until then, and for every card that starts no run. title: Charged Credits conversation_id: anyOf: - format: uuid type: string - type: 'null' title: Conversation Id decided_at: anyOf: - format: date-time type: string - type: 'null' title: Decided At decided_by_display_name: anyOf: - type: string - type: 'null' title: Decided By Display Name destructive: default: false description: >- Whether approving this removes something. A destructive card is drawn apart from the safe ones, is never offered a standing grant, and is listed on its own in the confirm an Approve all opens. title: Destructive type: boolean detail: anyOf: - $ref: '#/components/schemas/ProposalDetailSchema' - type: 'null' description: >- What the card shows under its summary, when one line is not enough to decide on: a prompt being rewritten, an email being reworded. Null for most cards, which say it all in the summary. error: anyOf: - type: string - type: 'null' description: Why an approval failed to apply, in plain words; null otherwise. title: Error expected_credits: anyOf: - type: number - type: 'null' description: >- What the run usually costs, in credits, read from what the same kind of cell has been charged before; equal to price_credits for a flat price, which the card then says as one figure. Null for a card whose price is the whole story. title: Expected Credits grantable: description: >- Whether the card may offer Approve and allow in this conversation: only a pending proposal of a verb that is not a send. title: Grantable type: boolean id: format: uuid title: Id type: string kind: $ref: '#/components/schemas/ProposalKind' description: >- `verb` for one of the eight workspace actions, `tool` for an API operation the assistant asked to call on your behalf. loss: anyOf: - type: string - type: 'null' description: >- What approving a destructive card takes away, and whether it comes back, in one sentence; null when nothing is removed. title: Loss message_id: anyOf: - format: uuid type: string - type: 'null' title: Message Id origin: $ref: '#/components/schemas/ProposalOrigin' prepared_column: anyOf: - $ref: '#/components/schemas/PreparedColumnSchema' - type: 'null' description: >- The column this card created before it was decided, so it can be opened from the card while it waits. Null for every other card. Approving runs the column; dismissing removes it, because adding it and running it were one decision. price_aside: anyOf: - type: string - type: 'null' description: >- What a waiting card says beside its Approve button, when the button does not say it all: "usually about 24", "Free", "Free to build · sending about 45 credits". Null when the button says everything. title: Price Aside price_credits: anyOf: - type: number - type: 'null' description: >- The published price of the operation when it was proposed, in credits; null when free. title: Price Credits price_label: description: >- What the card says it costs: "Free", or the most it can spend, "Up to 16.5 credits"; for a run charged by use, "Up to 65 credits · usually about 24"; for a flat price (a run of enrichments that each have one price), the one figure, "2,800 credits"; once that run has ended, "Charged 23.8 credits"; and for a card priced per day, "Up to 145 credits a day", before and after it is approved. title: Price Label type: string price_per: $ref: '#/components/schemas/PricePer' default: call description: >- What price_credits is the price of. `call`: the most approving this card may spend, once. `day`: the card starts something that keeps spending by itself (no tool raises one today), and price_credits is the most one day may cost ("Approve · up to 145 credits a day"). A total of several cards, such as Approve all's, leaves a `day` card out of its one-off sum. proposed_at: format: date-time title: Proposed At type: string runs_column_id: anyOf: - format: uuid type: string - type: 'null' description: >- The column approving this card runs, while the card waits: the one it added, or one already on the table that it names. Lets the column's own panel approve this card instead of starting a second run. Null for a card that runs no column, and once the card is decided. title: Runs Column Id source_column_id: anyOf: - format: uuid type: string - type: 'null' description: >- The agent column whose run raised the card; null for every other origin. What puts a card on its table's page when its arguments name a sequence or a destination instead of the table. title: Source Column Id source_record_id: anyOf: - format: uuid type: string - type: 'null' description: >- The row the agent was working on when it raised the card; null otherwise. title: Source Record Id status: $ref: '#/components/schemas/ProposalStatus' summary: title: Summary type: string verb: description: >- What the card proposes: one of the eight workspace verbs, or the name of an API operation the assistant asked to call. `kind` says which. title: Verb type: string verb_label: title: Verb Label type: string required: - id - origin - conversation_id - message_id - source_column_id - source_record_id - verb - kind - batch_id - verb_label - summary - price_credits - price_label - approve_label - price_aside - status - proposed_at - decided_at - decided_by_display_name - applied_result - error - grantable title: ActionProposalReadSchema 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 ActionConflictResponseSchema: description: >- A decision the proposal's state no longer allows: already decided, or not reversible. properties: detail: title: Detail type: string required: - detail title: ActionConflictResponseSchema 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 ProposalDetailSchema: description: |- The body of a card: what to read under the summary before approving. ``kind`` says how to draw it. ``text`` is a block to read; ``diff`` is a before and an after to compare, which is how a prompt or an email being rewritten is shown, so nobody approves a rewrite they have not seen. A card about a lead search also carries the search: under a ``text`` card's text, or as the first lines of a ``diff``'s before and after. The text then holds only what is not a filter. properties: after: default: '' description: What it would say, for a diff. title: After type: string before: default: '' description: What it says now, for a diff. title: Before type: string kind: enum: - text - diff title: Kind type: string landing: anyOf: - $ref: '#/components/schemas/CardLandingSchema' - type: 'null' description: The table a lead search would make, for a card that makes one. search: anyOf: - $ref: '#/components/schemas/CardSearchSchema' - type: 'null' description: >- The lead search whose filters the card lists, or the search after a diff. search_before: anyOf: - $ref: '#/components/schemas/CardSearchSchema' - type: 'null' description: The lead search as it stands, for a diff that changes one. text: default: '' description: The body, for a text card. title: Text type: string required: - kind title: ProposalDetailSchema type: object ProposalKind: description: >- How an approved card is carried out. VERB is F-15's eight hand-written workspace verbs: each has a spec in the registry with its own apply, because applying one is real work rather than a single request. TOOL is any route the assistant may call. An approval re-issues the request the model asked for, through the same executor an MCP client would use, so there is nothing to write per route and nothing to keep in step. enum: - verb - tool title: ProposalKind type: string ProposalOrigin: description: |- Which surface raised a proposal. Kept as its own enum rather than reusing the thread-store origins: a scheduled search proposes with no conversation behind it at all, and the activity feed needs to say so. enum: - chat - agent - scheduled_search - table_assistant title: ProposalOrigin type: string PreparedColumnSchema: description: >- The column a card created before anybody decided it. Adding a column and running it are one decision: the column lands the moment the card appears, so the person can open it and see what they are being asked to pay for, and the card quotes the run alone. Dismissing the card removes the column again. properties: column_id: anyOf: - format: uuid type: string - type: 'null' description: >- The column the card runs, when the card added it. Null when the card runs a column that was already on the table and added only columns that read it. title: Column Id dependent_column_ids: description: >- Columns the same reply added that the run fills in after this one. Dismissing the card removes them too. Empty for most cards. items: format: uuid type: string title: Dependent Column Ids type: array table_id: format: uuid title: Table Id type: string required: - table_id - column_id title: PreparedColumnSchema type: object PricePer: description: >- What a card's price is the price of: one call, or each day of what the call starts. CALL is nearly every card: the most approving it may spend, once. DAY is a card that starts (or re-arms) a standing buy that goes on spending by itself, adding rows every day: its price is the most one day may cost, said "up to 145 credits a day", and Approve all keeps it out of the one-off total it adds up. No tool starts one today. enum: - call - day title: PricePer type: string ProposalStatus: description: >- Where one proposed action stands. PROPOSED waits on a person. APPLIED happened. DISMISSED is a person saying no. FAILED is an approval whose apply raised; the error stays with the row so the card can say why instead of vanishing. UNDONE is HISTORY ONLY. Nothing reaches it any more: undo was taken out while the assistant moved from eight hand-written verbs to any route it may call, because reversing an arbitrary write is per-route work nobody has done yet. The member stays because rows in this state were written before that, and a status the code cannot read is an activity feed that raises instead of loading. enum: - proposed - applied - undone - dismissed - failed title: ProposalStatus 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 CardLandingSchema: description: >- The table a lead search's card would make: its name, how many it adds, a few who match. The card leads with it, so a person sees the list they asked for before approving it. Every word is the server's; the dashboard draws it as given. properties: adds: description: >- How many rows it adds out of how many match: "Adds 10 of 608 people". title: Adds type: string sample_columns: description: The sample's column names, as the table names them. items: type: string title: Sample Columns type: array sample_rows: description: >- A few who match, one value per column. Empty for a search whose rows are bought. items: items: type: string type: array title: Sample Rows type: array table_name: description: The new table's name, the card's title. title: Table Name type: string required: - table_name - adds title: CardLandingSchema type: object CardSearchSchema: description: |- A lead search a card lists the filters of, as the search route takes it. Drawn by the dashboard through the Find leads page's own summary, so a card names each filter as the page does, never by its route name. properties: query: additionalProperties: true description: The search's filters, filter name to value. title: Query type: object record_type: $ref: '#/components/schemas/LeadRecordType' description: Which lead search it is. required: - record_type title: CardSearchSchema type: object LeadRecordType: description: |- Which dataset a search runs against, and so which provider serves it. Values are persisted in String(16) columns, so every member must stay within 16 characters. enum: - people - companies - signal_companies - signal_people - lookalikes - local_businesses - hiring_companies - backlinks - search_results - post_authors title: LeadRecordType 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.