---
title: Zesty.io API Integration on Truto
slug: zesty
category: Application Development
canonical: "https://truto.one/integrations/detail/zesty/"
---

# Zesty.io API Integration on Truto



**Category:** Application Development  
**Status:** Generally available

## Unified APIs

### Unified User Directory API

- **Role Assignments** — 
- **Users** — The User object represents a User.
- **Workspaces** — Workspaces represent concepts like teams, workspaces, projects in apps that support them

## MCP-ready AI tools

Truto exposes 5 tools for Zesty.io that AI agents can call directly.

- **list_all_zesty_instances** — List all instances a user has access to in Zesty. Returns fields such as ZUID (unique identifier), name, domain, createdAt, updatedAt, blueprintZUID, screenshotURL, and other metadata for each instance.
- **get_single_zesty_instance_by_id** — Get a specific instance in Zesty.io by id (ZUID). Returns ZUID, name, domain, createdAt, updatedAt, and screenshotURL fields providing key instance details.
- **list_all_zesty_instance_users** — List all users for a specific instance in Zesty.io. Requires instance_zuid. Returns each user's ZUID, email, firstName, lastName, role, and timestamps for creation and updates.
- **list_all_zesty_instance_users_with_roles** — Get all users of a specific instance in Zesty.io using instance_zuid. Returns each user's details including ZUID, email, name, and their associated Role with its permissions and metadata.
- **list_all_zesty_user_instances** — Get user-instances for a specific user in Zesty.io using user_zuid. Returns instance details including name, ZUID, domain, blueprintZUID, createdAt, and updatedAt fields in the response.

## How it works

1. **Link your customer's Zesty.io account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach Zesty.io.** The Proxy API is a 1-to-1 mapping of the Zesty.io API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Audit user access across all Zesty.io instances** — Security and compliance SaaS products can pull user-role mappings across every Zesty.io instance to detect orphaned accounts, over-privileged users, or access policy violations — critical for customers in regulated industries like FinTech and healthcare.
- **Sync Zesty.io workspace membership into your product's tenant model** — SaaS platforms that serve multi-site enterprises can map Zesty.io instances to their own project or tenant structures, ensuring that the right users see the right workspaces without manual configuration.
- **Automate role-based task assignment from Zesty.io permissions** — Content localization, translation, or workflow platforms can read Zesty.io role assignments to automatically route approval tasks or publishing workflows only to users who hold the appropriate roles within a specific instance.
- **Build a unified directory of content team members** — HR, identity governance, or IT management tools can aggregate Zesty.io user directories alongside other SaaS applications using Truto's Unified User Directory API, giving admins a single pane of glass for user lifecycle management.
- **Visualize and manage a company's web property portfolio** — Digital operations and project management SaaS products can list all Zesty.io instances — including metadata like domains, blueprint IDs, and screenshot URLs — to auto-generate dashboards of an enterprise's active web properties.

## What you can build

- **Instance-to-project auto-mapping** — Automatically discover all Zesty.io instances a customer owns and let them link each instance to a corresponding project, campaign, or tenant in your product — complete with screenshot previews and domain metadata.
- **Cross-instance user access report** — Generate a consolidated report of every user, their email, and their role across all Zesty.io instances to surface access anomalies like dormant accounts or excessive admin privileges.
- **Role-aware permission mirroring** — Read Zesty.io role assignments per instance and automatically translate them into equivalent permission levels in your application, so a Zesty "Publisher" becomes an "Approver" in your platform without manual setup.
- **User onboarding and offboarding detection** — Periodically sync instance user lists to detect newly added or removed team members and trigger corresponding provisioning or deprovisioning workflows inside your product.
- **Web property inventory dashboard** — Pull instance details — name, domain, blueprint, and screenshot — via Truto's unified endpoints to render a live visual catalog of all Zesty.io-managed sites within your SaaS interface.
- **User-to-instance relationship explorer** — Let admins look up any team member and instantly see which Zesty.io instances they have access to, using the user-to-instance mapping endpoint to power a searchable directory view.

## FAQs

### What operations does Truto support for the Zesty.io integration?

Truto supports read operations for Zesty.io: listing all instances, fetching a single instance by ID, listing users per instance, listing users with their role assignments per instance, and listing all instances a specific user belongs to. These map to Truto's Unified User Directory API resources — Users, Workspaces, and Role Assignments.

### How does authentication work for Zesty.io through Truto?

Truto handles the authentication flow with Zesty.io on your behalf. Your end users connect their Zesty.io accounts through Truto's managed auth experience, so you don't need to build or maintain OAuth flows or API key management yourself.

### What user data is available from Zesty.io instances?

You can retrieve user profile fields including first name, last name, email, and Zesty unique ID (ZUID). When using the roles endpoint, you also get each user's assigned role and associated permission metadata for that specific instance.

### How are Zesty.io 'Instances' represented in the Unified User Directory API?

Zesty.io instances map to the Workspaces resource in Truto's Unified User Directory API. Each workspace includes properties like the instance name, domain, ZUID, blueprint ID, and screenshot URL.

### Does the integration support write operations like creating users or assigning roles?

Currently, the Zesty.io integration through Truto supports read-only operations — listing instances, users, and role assignments. Write operations such as user creation or role modification are not available at this time.

### How does Truto handle pagination for Zesty.io API responses?

Truto automatically manages pagination when calling Zesty.io's APIs. When you request a list of instances or users, Truto handles the underlying page traversal so you receive complete result sets without writing pagination logic yourself.
