Integrating with Terros: a technical overview

Short answers to the questions technical teams ask before an integration call, with links to the detailed sources. For the product view, see Integrations & API.

Which integration path fits

REST API

Read and write Terros data such as accounts, contacts, calendar events, users, tasks and reports over HTTPS at api.terros.com. Requests and responses are JSON.

Webhooks and Zapier

Outbound webhooks send Terros events to an endpoint you choose, and Zapier triggers on field activity.

Terros Connect

Connect packages an integration as an installable app that runs sandboxed scripts with its own secrets and logs. Ask us on a technical call about building one.

Terros CLI

The terros command calls API endpoints from a terminal, a script or an AI agent. It needs Node.js 24 or newer and installs with npm install -g @terros-inc/cli.

AI assistants (MCP)

Connect Claude, ChatGPT, Cursor or another MCP client to https://mcp.terros.com/mcp and sign in with your Terros account; it can see and do only what your role allows, and it is read-only unless you enable changes.

Authentication and access

API keys

A company admin, or a user allowed to create API keys, adds keys on the API Keys page in company settings and sets each key's description, expiration and permissions. The key is shown once: store it in a secret manager, use it only server-side, and revoke and replace it if it is exposed.

Sending the key

Send Authorization: ApiKey followed by your key on every request to https://api.terros.com.

CLI sign-in

terros auth login signs you in through your browser. It needs developer mode on your Terros account, which needs the user:developer permission from your company admin.

Requests and errors

One request shape

Every endpoint is a POST with a JSON body. The OpenAPI spec describes each one.

Errors in the body

Responses return HTTP 200, so check the JSON body: an error has type error, an error type and a message. HTTP 401, 403 and 500 appear only in specific cases.

How changes are communicated

When the data model changes, the docs publish a migration guide. The workflow migration guide shows legacy fields kept in responses during the transition.

Imports and exports

Bulk import

Import accounts, calendar events, users, tasks and recruits from CSV, and areas from KML or KMZ. Imports are asynchronous: start one, upload the file, then poll until it finishes.

Exports

Export accounts, calendar events, users, tasks and activity. Canvass map and territory data stays in the app.

Status

Status page

status.terros.com shows current status and 30-day uptime history for the mobile app, web app, API, docs and help center. Subscribe to updates by email, Slack or webhook.

Security and compliance

SOC 2 Type II

Terros maintains a SOC 2 Type II report covering Security, with an unqualified opinion and no exceptions noted. Request the report and see the bridge letter on the trust center.

Reporting a vulnerability

Our security policy explains how to report a suspected vulnerability.

Common integrations

CRMs and tools

Two-way sync with Salesforce and HubSpot; connections to Enerflo, JobNimbus, ServiceTitan and Airtable; Zapier; Google Sheets exports; and Google Calendar and Outlook sync.

Ask us on a technical call

Bring the questions this page does not answer, such as rate limits, webhook delivery, test environments, API versioning, data retention and hosting, single sign-on, security questionnaires, how each company's data is kept separate, service levels and rollout plans.