affiliate14

agent-training10

ai_apps5

ai-context14

apikey7

app-listings6

assistant20

assistant-prompt4

attribution1

billing8

contact_cooldown2

credits12

design-partner4

find-leads25

find-subdomains3

google-drive5

helpscout1

inbox31

inbox-ai10

integration-types5

integrations13

linkedin23

notifications10

onboarding2

outbound-agents20

outreach17

referral5

senders32

sequences100

suppression4

table-column-color-labels2

table-columns25

table-enrichment-audit-logs1

table-enrichments31

table-events1

table-export1

table-imports5

table-integration-lookup2

table-rows16

table-runs3

table-schedules4

table-sources13

table-templates4

table-ui-prefs1

table-user-prefs4

table-views5

table-writeback4

tables31

workspace-actions10

workspace-actions

Approve a proposed action

Apply a proposal on your say-so. Idempotent: approving an action that already applied returns it unchanged, so a second click applies nothing twice. An action whose apply is refused (the balance is empty, or cannot cover what has to be paid before it starts; the object it names is gone) comes back failed with the reason on the card, not as an error. A run charged as it fills may start when the most it could cost is more than the balance: it stops when the credits run out and keeps what it filled.

scope says whether the next one like it should still ask: once decides this card alone, thread allows the operation for the rest of the conversation, project_me allows it for you across the workspace and project_all for everybody in it. A send is never grantable and asks again whatever is chosen.

post/assistant/actions/{proposal_id}/approve/

Request

Base URL: https://api.getoneprofile.ai (the document declares no server; this is the origin it was published from)
URL: https://api.getoneprofile.ai/assistant/actions/{proposal_id}/approve/
Auth: one of:
- API key in header X-API-Key
- HTTP bearer

Path parameters

proposal_idstring uuid required

Request body

scope'once' | 'thread' | 'project_me' | 'project_all'

Response

Successful Response

applied_resultobject nullable required

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.

approve_labelstring required

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".

batch_idstring uuid nullable required

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.

charged_creditsnumber nullable

What the run this card started was charged, in credits, once it finished. Null until then, and for every card that starts no run.

conversation_idstring uuid nullable required

decided_atstring date-time nullable required

decided_by_display_namestring nullable required

destructiveboolean

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.

errorstring nullable required

Why an approval failed to apply, in plain words; null otherwise.

expected_creditsnumber nullable

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.

grantableboolean required

Whether the card may offer Approve and allow in this conversation: only a pending proposal of a verb that is not a send.

idstring uuid required

kind'verb' | 'tool' required

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.

lossstring nullable

What approving a destructive card takes away, and whether it comes back, in one sentence; null when nothing is removed.

message_idstring uuid nullable required

origin'chat' | 'agent' | 'scheduled_search' | 'table_assistant' required

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.

price_asidestring nullable required

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.

price_creditsnumber nullable required

The published price of the operation when it was proposed, in credits; null when free.

price_labelstring required

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.

price_per'call' | 'day'

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.

proposed_atstring date-time required

runs_column_idstring uuid nullable

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.

source_column_idstring uuid nullable required

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.

source_record_idstring uuid nullable required

The row the agent was working on when it raised the card; null otherwise.

status'proposed' | 'applied' | 'undone' | 'dismissed' | 'failed' required

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.

summarystring required

verbstring required

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.

verb_labelstring required

Changes

No recorded changes to this operation across all 1 revision of this API.