Serversmtp TurboSMTP Public APIs

Name: TurboSMTP Public APIs
Brand: TurboSMTP Public APIs
Availability: InStock

✓ Official Vendor SpecMarketingEmail MarketingapiKey40 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the TurboSMTP Public APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TurboSMTP Public APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with TurboSMTP Public APIs.

Logout and invalidate token

Change account password

Request forgot password email

GET STARTED

Start building with TurboSMTP Public APIs

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use TurboSMTP Public APIs for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

40 endpoints — turbosmtp is a professional smtp service for reliable, secure email and newsletter delivery.

METHOD

PATH

DESCRIPTION

POST

/authorize

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

POST

/authorize

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

TurboSMTP Public APIs apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'login and get authorization token') and Jentic returns the matching TurboSMTP Public APIs operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct TurboSMTP Public APIs integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using TurboSMTP Public APIs through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

Serversmtp TurboSMTP Public APIs

Connect the TurboSMTP Public APIs to your agent

Capabilities

Start building with TurboSMTP Public APIs

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs