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

# Serversmtp TurboSMTP Public APIs

TurboSMTP is a professional SMTP service for reliable, secure email and newsletter delivery. This API provides endpoints for sending emails, managing suppressions, email validation, sub-account management, and more. The API exposes 40 endpoints secured with apiKey authentication.

## For AI agents

Programmatically login and get authorization token, logout and invalidate token. Covers 40 operations with apiKey authentication.

## Scope

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

## Capabilities

- Login and get authorization token
- Logout and invalidate token
- Change account password
- Request forgot password email
- Check forgot password token
- Reset password with token
- Send an email

## Use cases

### Marketing Operations

Use the TurboSMTP Public APIs to perform marketing operations programmatically. The API provides 40 endpoints covering core functionality including login and get authorization token, logout and invalidate token, change account password.

Example prompt: Call POST /authorize to login and get authorization token

### Automated Authentication Management

Automate authentication operations by combining multiple TurboSMTP Public APIs endpoints. Agents can logout and invalidate token and then change account password in a single workflow.

Example prompt: Call POST /deauthorize to logout and invalidate token, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TurboSMTP Public APIs 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 apiKey tokens manually.

Example prompt: Search Jentic for 'login and get authorization token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/authorize` | Login and get authorization token |
| POST | `/deauthorize` | Logout and invalidate token |
| PUT | `/change-password` | Change account password |
| POST | `/forgot-password` | Request forgot password email |
| GET | `/forgot-password` | Check forgot password token |
| PUT | `/forgot-password` | Reset password with token |
| POST | `/mail/send` | Send an email |
| POST | `/suppressions` | Add a suppressed email address |

## Key resources

- **Authentication** — Login, logout, password management
- **Mail** — Email sending operations
- **Suppressions** — Managing suppressed email addresses
- **Meta** — Metadata endpoints (countries, states)
- **Billing** — Credit and subscription management

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 70 / 100
- **View full report:** https://jentic.com/apis/serversmtp.com/serversmtp/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 TurboSMTP by hand means calling /authorize for a key, choosing the right EU or US send host, and attaching the Authorization header to every mail and suppression call yourself. Through Jentic you install once, import TurboSMTP from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** TurboSMTP carries the send target in the request body, not the URL path, so limit the agent to the operations it needs, such as sending mail or managing suppressions. You choose the operations it may call, so password changes or subaccount deletion are not included unless you add them.
- **Credential handling:** Your TurboSMTP 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 'send an email' or 'add a suppression', and Jentic returns the matching TurboSMTP operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the TurboSMTP Public APIs use?

The TurboSMTP Public APIs uses an API key passed 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 login and get authorization token with the TurboSMTP Public APIs?

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

### What are the rate limits for the TurboSMTP Public APIs?

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 login and get authorization token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login and get authorization token'. Jentic returns the matching TurboSMTP Public APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TurboSMTP Public APIs have?

The TurboSMTP Public APIs exposes 40 endpoints covering authentication, mail, suppressions operations.

### Can I limit what my agent is allowed to do with the TurboSMTP Public APIs?

Yes. Because you run Jentic One yourself, you decide which TurboSMTP operations your agent can call and which stored credentials it may use. You can allow only the operations it needs, such as sending mail through `/mail/send` or managing suppressions through /suppressions, while leaving out sensitive actions like changing the account password or deleting sub-accounts. Since TurboSMTP carries the send target in the request body rather than the URL path, scoping is enforced at the operation level by your own rules.