> ## 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. # Preview trying a Browser use step on one contact > What trying the step on this contact would do, starting nothing: who the agent would act as (the mailbox that emails the contact, else the one a run would assign them) and the most it may charge. Refuses a step or a contact that cannot be tried, as the start would. While the step's own trial is in line or running it answers `already_running` and that trial, since a start would then start nothing. ## OpenAPI ````yaml /openapi.json post /sequences/{sequence_id}/steps/{step_id}/browser-trials/preview/ 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: /sequences/{sequence_id}/steps/{step_id}/browser-trials/preview/: post: tags: - sequences summary: Preview trying a Browser use step on one contact description: >- What trying the step on this contact would do, starting nothing: who the agent would act as (the mailbox that emails the contact, else the one a run would assign them) and the most it may charge. Refuses a step or a contact that cannot be tried, as the start would. While the step's own trial is in line or running it answers `already_running` and that trial, since a start would then start nothing. operationId: preview_browser_trial parameters: - in: path name: sequence_id required: true schema: format: uuid title: Sequence Id type: string - in: path name: step_id required: true schema: format: uuid title: Step Id type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/BrowserTrialCreateSchema' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/BrowserTrialPreviewSchema' description: Successful Response '401': content: application/json: schema: $ref: '#/components/schemas/UnauthorizedResponse' description: Unauthorized '402': content: application/json: schema: $ref: '#/components/schemas/PaymentRequiredResponse' description: The workspace has no credits left. '403': content: application/json: schema: $ref: '#/components/schemas/ForbiddenResponse' description: Forbidden '404': content: application/json: schema: $ref: '#/components/schemas/NotFoundResponse' description: Not found. '422': content: application/json: schema: $ref: '#/components/schemas/UnprocessableEntityResponse' description: The step or the contact cannot be tried; the message says why. '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: BrowserTrialCreateSchema: description: Which contact of the audience to try a Browser use step on. properties: record_id: description: The audience row. format: uuid title: Record Id type: string required: - record_id title: BrowserTrialCreateSchema type: object BrowserTrialPreviewSchema: description: >- What trying a Browser use step on one contact would do, before it starts. properties: acts_as_address: anyOf: - type: string - type: 'null' description: >- The mailbox the agent would act as: the one that emails the contact, else the one a run would assign them (not recorded by a trial). Null when already running. title: Acts As Address acts_as_name: anyOf: - type: string - type: 'null' description: >- The sender the agent would act as for this contact; null when one runs. title: Acts As Name already_running: description: >- The step's trial is already in line or running, so a trial asked for now would start nothing: one trial of a step at a time. title: Already Running type: boolean max_credits: description: >- The most the trial may charge: every minute it may use, at the price. title: Max Credits type: number trial: anyOf: - $ref: '#/components/schemas/BrowserTrialReadSchema' - type: 'null' description: >- The step's trial already in line or running; null when there is none. required: - already_running - trial - max_credits title: BrowserTrialPreviewSchema type: object UnauthorizedResponse: properties: detail: description: The detail of why the request is unauthorized. title: Detail type: string required: - detail title: UnauthorizedResponse type: object PaymentRequiredResponse: properties: detail: description: The detail of why payment is required. title: Detail type: string required: - detail title: PaymentRequiredResponse 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 BrowserTrialReadSchema: description: >- A Browser use step's trial on one contact: who, as whom, and what it did. properties: acts_as: anyOf: - type: string - type: 'null' description: The mailbox the agent acted as; null until its browser was claimed. title: Acts As contact_label: anyOf: - type: string - type: 'null' description: >- The contact's name off their row, else their address; null once gone. title: Contact Label created_at: format: date-time title: Created At type: string id: description: The trial, for its replay and its hidden values. format: uuid title: Id type: string record_id: description: The audience row it was tried on. format: uuid title: Record Id type: string run: $ref: '#/components/schemas/BrowserRunReadSchema' description: >- What it did, in a contact's run's own shape. A trial never moves its contact, writes a cell or counts in the step's numbers. step_id: format: uuid title: Step Id type: string required: - id - step_id - record_id - created_at - run title: BrowserTrialReadSchema 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 BrowserRunReadSchema: description: What one Browser use run did for the contact. properties: billed_minutes: default: 0 description: >- The browser minutes the run was billed for: its browser's length, rounded up, never past a run's most minutes. 0 until it settles, and for a run whose browser never opened. title: Billed Minutes type: integer charged_credits: description: >- What the run was charged: its browser's minutes, rounded up, at the per-minute price. 0 until it settles, and for a run whose browser never opened. title: Charged Credits type: number failure: anyOf: - type: string - type: 'null' description: >- Why it ended without the agent's choice: time_limit, budget, interrupted, page_unreadable, model_error, unavailable or out_of_credits (the workspace's credits could not hold its next stretch of browsing). Null when the agent chose. title: Failure finished_at: anyOf: - format: date-time type: string - type: 'null' title: Finished At has_replay: description: Whether its browser opened, so a recording may exist. title: Has Replay type: boolean last_refusal: anyOf: - $ref: '#/components/schemas/BrowserRefusal' - type: 'null' description: >- While the run waits in line: why the cloud browser refused its last start. capacity (every browser in use) reads Waiting for browser; unavailable (an outage at the vendor) reads Browser use is unavailable right now. Either way it is tried again on its own and nothing is charged. Null once its browser opens. outcome_key: anyOf: - type: string - type: 'null' description: 'The branch it took: one of the step''s outcome slots, or needs_human.' title: Outcome Key outcome_label: anyOf: - type: string - type: 'null' description: That outcome's words, as the step named it when it settled. title: Outcome Label outputs: description: >- The values the run looked for or found, once it settled. A value it never got to is not listed; one it looked for and did not find has found false. items: $ref: '#/components/schemas/BrowserRunOutputReadSchema' title: Outputs type: array reason: anyOf: - type: string - type: 'null' description: Why, in one sentence. title: Reason run_id: description: The run, for its replay. format: uuid title: Run Id type: string started_at: anyOf: - format: date-time type: string - type: 'null' title: Started At status: $ref: '#/components/schemas/BrowserRunStatus' description: queued while it waits for a browser, running, or settled once over. steps: description: What the agent did, in order. items: $ref: '#/components/schemas/AiStep' title: Steps type: array required: - run_id - status - has_replay - charged_credits title: BrowserRunReadSchema type: object BrowserRefusal: description: >- Why the cloud browser refused a run's start, before any browser command went out. Either way the run goes back in line unstarted and is tried again (``sequence_browser_run.last_refusal``): nothing ran, so nothing is charged and nobody is asked. enum: - capacity - unavailable title: BrowserRefusal type: string BrowserRunOutputReadSchema: description: One value a Browser use run brought back. properties: found: description: >- Whether the run brought a value back. True for a hidden value it kept, which a reveal shows; false when it found nothing, so there is nothing to reveal. title: Found type: boolean hidden: title: Hidden type: boolean key: title: Key type: string name: description: The value's name on the step; its key once the step drops it. title: Name type: string value: anyOf: - type: string - type: 'null' description: >- What the run found. Null for a value it did not find, and for a hidden one (a password the run made), which only an audited reveal shows. title: Value required: - key - name - hidden - found title: BrowserRunOutputReadSchema type: object BrowserRunStatus: description: >- Where one Browser use run stands on its ledger row (``sequence_browser_run.status``). ``QUEUED`` waits in the platform's line for a browser; ``RUNNING`` was started by the dispatcher and holds a lease (``lease_until``); ``SETTLED`` is over, whether it reached an outcome or never ran. enum: - queued - running - settled title: BrowserRunStatus type: string AiStep: additionalProperties: false description: >- One thing an AI turn did, as the wire spells it. Field-for-field identical to ``table_live_updates.TableCellActivityStepSchema`` ON PURPOSE, and the duplication is the design. That schema sits in the table stratum's kernel, which the lead search, inbox and sequence surfaces have no business importing; this one sits under every surface equally. Because the two agree exactly, the frontend's ``TimelineStep`` renders both with no conversion and no second component, which is the property worth protecting. ``test_ai_step_mirrors_the_cell_activity_step`` pins them together. Plain strings rather than enums, for the same reason the cell schema uses them: the vocabulary is open, clients must tolerate tokens they have not learned yet, and a new action should never be able to break a running dashboard. properties: action: description: >- What kind of move this was, e.g. `read_table`, `plan`, `write_column`. title: Action type: string detail: default: '' description: >- The step's input: the instruction, the column it read, the query it ran. title: Detail type: string duration_ms: anyOf: - type: integer - type: 'null' description: Wall clock for the work this step describes, never an estimate. title: Duration Ms observation: default: '' description: >- One line on what came back. The half that makes a step worth reading. maxLength: 500 title: Observation type: string outcome: default: completed description: >- `completed`, `failed`, `refused` or `stopped`. Clients must tolerate new tokens. title: Outcome type: string thought: anyOf: - type: string - type: 'null' description: >- The model's stated reasoning for choosing this step. Set by the agent loop; the assistant surfaces leave it null, and the renderer simply omits the rung. title: Thought required: - action title: AiStep 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.