Developers and integrations

Connect Rowvia tables to agents and your own systems

Choose the integration path by who will work with the tables: an AI agent through MCP, or your backend and scripts through the REST API. The default add flow is one primary source per row; extended rows can also carry related attachments.

ChatGPT connector

ChatGPT uses Rowvia OAuth

The ChatGPT web connector uses https://api.rowvia.ai/mcp and Rowvia OAuth. The user does not create, copy, or paste an rvia_ API token.

Open MCP documentation
Local MCP clients

Local MCP uses an env token

Claude Desktop, Cursor, Codex CLI, and local agents use stdio config. The rvia_... token belongs in the ROWVIA_API_TOKEN environment variable.

Open MCP documentation
REST API

REST API uses a Bearer token

Your backend, scheduled jobs, and scripts send Authorization: Bearer rvia_.... Create the token in Profile -> Integrations and restrict it to a table when possible.

Open REST API documentation

Token safety

  • Never paste an rvia_ token into a shared chat, prompt, or document.
  • Do not put the token in a browser frontend, public JavaScript, or client bundle.
  • Do not send tokens in URLs, query parameters, or imported links.
  • Prefer a table-restricted token for repeated workflows.
  • Start larger processing runs only after confirming the target table and pending-work estimate.
  • Log request_id or processing_run_id, never the full token.

Validate the workflow in the app first

Prepare the table and template manually, check the columns and source model. The baseline is one primary document, URL, or text source per row; when a workflow needs attachments for one case, keep them on the same row before connecting the process through MCP or the REST API.

Open appTry the demo