API & Integrations

GigRoot offers a public API so you can connect your website, forms, and other systems directly to your workspace. The most common use is capturing leads automatically — when someone fills in a form on your site, create a lead in GigRoot without any manual entry.

Requests are authenticated with an API key tied to your workspace. Generate a key from your settings, keep it secret (treat it like a password), and send it with each request. Rotate or revoke keys if one is ever exposed.

The GigRoot CLI signs a terminal in to your account and creates documents in the Documents module — useful when the thing writing the document is a script or an AI agent rather than a person at a keyboard.

Run gigroot login. It shows a short code and opens GigRoot in your browser; you approve there, already signed in, and the terminal is connected. Nothing is pasted into the terminal, and the connection can be revoked in Settings, which stops that machine immediately.

Then gigroot doc create report.md --title "Q3 Report" creates the document and prints its URL. Markdown and HTML are both accepted, and the result is an ordinary GigRoot document — it opens in the editor and can be shared, exported and edited by hand afterwards.

GigRoot is an MCP server, so Claude — or any client that speaks the Model Context Protocol — can read and update your workspace in conversation: look up leads and deals, list deliverables, check attendance, create tasks and outreach, and more.

1. 1
   Add the connector

   In your AI client, add https://mcp.gigroot.co as a connector. You are sent to GigRoot to sign in and Approve the connection.
2. 2
   Or use a key

   For clients that take a bearer token, the owner creates one in Settings → Privacy & security → API Keys. The key is shown once; keep it secret.

The client acts as the person who connected it, through the same permission rules as the app: it sees only what that person may see, and can only change what they may change. Around 90 tools cover every module, most of them read-only. Revoke a key or connection from the same API Keys list and it stops at once.

Post a new lead to POST /v1/leads with the lead's details and your API key. The lead appears in your CRM ready to work, just like one created by hand. Any custom fields you have defined can be included in the request, so the API captures exactly the data your process needs.

This page is a friendly overview. For the complete developer reference — endpoints, request and response formats, and an interactive playground — visit the Developers page.