canonical: https://jentic.com/apis/syncromsp.com/syncromsp

# Syncromsp Syncro API

Syncro MSP platform API for managing IT service business operations including tickets, customers, assets, appointments, contacts, and contracts. The API exposes 30 endpoints secured with bearer authentication.

## For AI agents

Programmatically create appointment type, list appointment types. Covers 30 operations with bearer authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Create appointment type
- List appointment types
- Get appointment type
- Update appointment type
- Delete appointment type

## Use cases

### CRM Operations

Use the Syncro API to perform crm operations programmatically. The API provides 30 endpoints covering core functionality including create appointment type, list appointment types, get appointment type.

Example prompt: Call POST `/v1/appointment_types` to create appointment type

### Automated Appointment Types Management

Automate appointment types operations by combining multiple Syncro API endpoints. Agents can list appointment types and then get appointment type in a single workflow.

Example prompt: Call GET `/v1/appointment_types` to list appointment types, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Syncro 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 bearer tokens manually.

Example prompt: Search Jentic for 'create appointment type', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/appointment_types` | Create appointment type |
| GET | `/v1/appointment_types` | List appointment types |
| GET | `/v1/appointment_types/{id}` | Get appointment type |
| PUT | `/v1/appointment_types/{id}` | Update appointment type |
| DELETE | `/v1/appointment_types/{id}` | Delete appointment type |
| POST | `/v1/appointments` | Create appointment |
| GET | `/v1/appointments` | List appointments |
| GET | `/v1/appointments/{id}` | Get appointment |

## Key resources

- **Appointment Types** — Operations related to Appointment Types
- **Appointments** — Operations related to Appointments
- **Assets** — Operations related to Assets
- **Contacts** — Operations related to Contacts
- **Contracts** — Operations related to Contracts

## Why Jentic

- **Setup:** Wiring the Syncro API by hand means learning its bearer token scheme, resolving your own subdomain.syncromsp.com host, and shaping the appointment and appointment-type requests yourself. Through Jentic you install once, import Syncro from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Syncro puts the record id in the URL path (`/v1/appointments/{id}`), so a rule can pin your agent to one appointment: it can read and update that record and nothing else. You choose the operations it may call, so destructive ones like deleting an appointment or appointment type are not included unless you add them.
- **Credential handling:** Your Syncro bearer token 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 an appointment type' or 'list appointments', and Jentic returns the matching Syncro operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Syncro API use?

The Syncro API uses a Bearer token in the Authorization header. 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 appointment type with the Syncro API?

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

### What are the rate limits for the Syncro 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 appointment type through Jentic?

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

### How many endpoints does the Syncro API have?

The Syncro API exposes 30 endpoints covering appointment types, appointments, assets operations.

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

Yes. Because you run Jentic One yourself, you decide which Syncro operations your agent may call and which bearer credential it uses, so you can allow read and update calls while leaving out destructive ones like deleting an appointment or appointment type. Since Syncro puts the record id in the URL path, such as `/v1/appointments/{id}`, you can pin the agent to a single appointment so it can read and update that record and nothing else. Only the operations you explicitly grant are available to the agent.