canonical: https://jentic.com/apis/zoho.com/zoho-fsm-api

# Zoho FSM API

Zoho FSM provides REST API (Application Programming Interface) that lets you integrate FSM with third-party applications for inventory management, forecasting, and business intelligence. The REST API uses simple HTTP methods, such as GET, POST, PUT and DELETE. These methods allow FSM data to be extracted in JSON format including errors, making it easy to develop new applications and also to integr. The API exposes 34 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create a work order, list work orders. Covers 34 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Create a work order
- List work orders
- Get work order details
- Update work order
- Delete work order

## Use cases

### E-Commerce Operations

Use the Zoho FSM API to perform e commerce operations programmatically. The API provides 34 endpoints covering core functionality including create a work order, list work orders, get work order details.

Example prompt: Call POST /workorders to create a work order

### Automated Work Orders Management

Automate work orders operations by combining multiple Zoho FSM API endpoints. Agents can list work orders and then get work order details in a single workflow.

Example prompt: Call GET /workorders to list work orders, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Zoho FSM API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'create a work order', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /workorders | Create a work order |
| GET | /workorders | List work orders |
| GET | /workorders/{workorder_id} | Get work order details |
| PUT | /workorders/{workorder_id} | Update work order |
| DELETE | /workorders/{workorder_id} | Delete work order |
| POST | /appointments | Create service appointment |
| GET | /appointments | List service appointments |
| GET | /appointments/{appointment_id} | Get appointment details |

## Key resources

- **Work Orders** — Manage work orders for field service operations
- **Service Appointments** — Schedule and manage service appointments
- **Technicians** — Manage field technicians and workforce
- **Customers** — Manage customer information and contacts
- **Service Requests** — Handle service requests from multiple channels

## Why Jentic

- **Setup:** Wiring Zoho FSM by hand means running its OAuth 2.0 flow, refreshing tokens, and picking the right regional host among fsm.zoho.com, .eu, .in, and .com.au yourself. Through Jentic you install once, import Zoho FSM from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** Zoho FSM puts the work order id in the URL path (/workorders/{workorder_id}), so a rule can pin your agent to one work order: it can read and update that work order and nothing else. You choose the operations it may call, so destructive ones like work order or appointment deletion are not included unless you add them.
- **Credential handling:** Your Zoho FSM OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a work order' or 'schedule an appointment', and Jentic returns the matching Zoho FSM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Zoho FSM API use?

The Zoho FSM API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create a work order with the Zoho FSM API?

Yes. Use the POST /workorders endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Zoho FSM API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create a work order through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a work order'. Jentic returns the matching Zoho FSM API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Zoho FSM API have?

The Zoho FSM API exposes 34 endpoints covering work orders, service appointments, technicians operations.

### Can I limit what my agent is allowed to do with the Zoho FSM API?

Yes. Because you run Jentic One yourself, your own rules decide which Zoho FSM operations and which OAuth credential the agent may use. Since the work order id sits in the URL path (/workorders/{workorder_id}), you can pin the agent to a single work order so it only reads and updates that record. You choose the operations it may call, so destructive ones such as work order or appointment deletion stay off the list unless you explicitly add them.