Gettruss Truss API

Name: Truss API
Brand: Truss API
Availability: InStock

✓ Official Vendor SpecProductivityCollaborationbearer43 EndpointsREST

For Agents

Manage projects, tasks, contacts, and drive folders in the Truss platform via 43 endpoints with bearer-token authentication.

Install Jentic One Beta

Connect the Truss API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Truss API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Truss API.

Create and update projects with custom statuses and metadata fields

Assign and update tasks tied to specific projects and users

Search contacts by name or attribute and retrieve a contact-picker dropdown

Look up projects by idempotency key to prevent duplicate creation

GET STARTED

Start building with Truss API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Truss API for, with concrete tasks.

★ Sync Project Data with External Tools

Operations teams running Truss alongside CRMs, billing tools, or BI dashboards need project records to flow both ways. The Truss API exposes list and update on projects, plus idempotency-key lookup so a sync job can safely re-run without creating duplicates. Pair this with the metadata-key list endpoint to slice projects by external identifier.

List projects with metadata key 'crm_id=987', then update each project's status field to 'in-review'.

Automated Task Assignment

When a new client signs a contract or a deal closes in another system, a downstream workflow can create the associated tasks in Truss automatically. The tasks resource accepts a project id, owner, and due date so the agent or workflow tool spins up the full task list without manual entry. The contact-search endpoint resolves owner names to user records first.

For each task in the kickoff template, create it in project 555 with the matching owner resolved via /contacts/search.

Contact Search and Picker UIs

Internal tools that mirror the Truss contact list use GET /contacts/search for autocomplete and GET /contacts/dropdown for the standard picker. This avoids loading the full contact list into the browser and keeps response sizes small for high-traffic admin tools.

Call GET /contacts/search with query 'acme' and return the first 10 matching contacts.

AI Agent Project Operations

AI agents triaging email or chat into Truss can create projects, attach contacts, and update statuses without UI navigation. Through Jentic the agent finds the right operation by intent ('create a project' or 'update project status'), loads its schema, and executes — Truss bearer tokens stay in the Jentic vault rather than reaching the agent context.

Create a project named 'Acme Q2 Onboarding' with idempotency key 'acme-q2-2026' and assign the contact id returned by /contacts/search.

Key Endpoints

43 endpoints — the truss api provides programmatic access to the truss file collection and project management platform.

METHOD

PATH

DESCRIPTION

POST

/projects

Create a new project

GET

/projects/get_by_idempotency_key

Look up a project by idempotency key

POST

/projects/{id}/update_status

Change project status

GET

/projects/list_by_metadata_key

List projects filtered by metadata key

GET

/contacts/search

Search contacts by query

GET

/contacts/dropdown

Get contact picker dropdown payload

POST

/projects

Create a new project

GET

/projects/get_by_idempotency_key

Look up a project by idempotency key

POST

/projects/{id}/update_status

Change project status

GET

/projects/list_by_metadata_key

List projects filtered by metadata key

GET

/contacts/search

Search contacts by query

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Truss bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped invocation capability — the raw token never enters the agent's context, so a leaked prompt does not leak the Truss credential.

Intent-based discovery

Agents search by intent (e.g. 'create a project' or 'update project status') and Jentic returns the matching Truss operation with its full input schema for direct execution.

Time to first call

Direct Truss integration including auth, idempotency, and contact-search wiring: 1-2 days. Through Jentic: under 1 hour — search, load, execute.

FAQs

Specific to using Truss API through Jentic.

What authentication does the Truss API use?

Truss uses HTTP bearer authentication — clients send Authorization: Bearer <token> on every request. Through Jentic this token is stored encrypted in the vault and the agent only receives a scoped capability to invoke specific Truss operations.

Can I create a new project with the Truss API?

Yes. POST /projects accepts the project payload and returns the created record. Pair this with GET /projects/get_by_idempotency_key on retry so the same idempotency key always resolves to one project, never a duplicate.

What are the rate limits for the Truss API?

The spec does not declare explicit limits. Production integrations should respect 429 responses with backoff and avoid tight loops over /projects or /contacts; cache the contact dropdown payload where possible since it is a heavy response.

How do I update a project status with Truss through Jentic?

Search Jentic for 'change truss project status'. Jentic returns POST /projects/{id}/update_status with its input schema; load it, supply the project id and target status, and execute. The response confirms the new status.

Can I search Truss contacts by name?

Yes. GET /contacts/search accepts a query string and returns matching contact records. For lighter UI use cases GET /contacts/dropdown returns the picker-ready list without full contact bodies.

Gettruss Truss API

Connect the Truss API to your agent

Capabilities

Start building with Truss API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs