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

# SYNDUIT API

SYNDUIT marketing automation API for managing contacts, tags, dynamic fields, and webhook subscriptions. The API exposes 16 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically verify oauth token, create a contact. Covers 16 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Verify OAuth token
- Create a contact
- List all contacts
- Get a specific contact
- Update a contact
- Delete a contact

## Use cases

### Payments Operations

Use the SYNDUIT API to perform payments operations programmatically. The API provides 16 endpoints covering core functionality including verify oauth token, create a contact, list all contacts.

Example prompt: Call GET /me to verify oauth token

### Automated Auth Management

Automate auth operations by combining multiple SYNDUIT API endpoints. Agents can create a contact and then list all contacts in a single workflow.

Example prompt: Call POST /contacts to create a contact, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SYNDUIT 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 'verify oauth token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/me` | Verify OAuth token |
| POST | `/contacts` | Create a contact |
| GET | `/contacts` | List all contacts |
| GET | `/contacts/{id}` | Get a specific contact |
| PUT | `/contacts/{id}` | Update a contact |
| DELETE | `/contacts/{id}` | Delete a contact |
| GET | `/dynamic-fields` | List all dynamic fields |
| POST | `/tags` | Create a tag |

## Key resources

- **Auth** — Operations related to Auth
- **Contacts** — Operations related to Contacts
- **Tags** — Operations related to Tags
- **Webhooks** — Operations related to Webhooks

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 76 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 90 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/synduit.com/synduit/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the SYNDUIT API by hand means implementing its OAuth2 authorization-code flow against api.synduit.com, exchanging codes for tokens and refreshing them, then shaping the contact and tag requests yourself. Through Jentic you install once, import SYNDUIT from the API Directory, store the OAuth2 credentials once, and your agent calls it.
- **Permission scoping:** SYNDUIT puts the contact id in the URL path (`/contacts/{id}`), so a rule can pin your agent to one contact: it can read and update that record and nothing else. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.
- **Credential handling:** Your SYNDUIT OAuth2 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a contact' or 'verify the OAuth token', and Jentic returns the matching SYNDUIT operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the SYNDUIT API use?

The SYNDUIT 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 verify oauth token with the SYNDUIT API?

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

### What are the rate limits for the SYNDUIT 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 verify oauth token through Jentic?

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

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

The SYNDUIT API exposes 16 endpoints covering auth, contacts, tags operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Synduit operations and credentials the agent may use. Because Synduit puts the contact id in the URL path (`/contacts/{id}`), you can pin the agent to a single contact so it only reads and updates that record. You also choose the operations it may call, so destructive endpoints like DELETE `/contacts/{id}` stay off limits unless you explicitly add them.