Install Jentic One Beta

Connect the Sendmsg API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sendmsg API, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsendmsg.co.il%2Fsendmsg-co-il" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsendmsg.co.il%2Fsendmsg-co-il" | 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 Sendmsg API.

Get authentication token

Test authentication

Add or update users

Query and filter Sendmsg API records by parameters

Monitor Sendmsg API operational status and events

GET STARTED

Start building with Sendmsg API

Explore with Jentic One

View OpenAPI Document

Automated Authentication Management

Automate authentication operations by combining multiple Sendmsg API endpoints. Agents can test authentication and then add or update users in a single workflow.

Call POST /ping to test authentication, then verify the result

AI Agent Integration via Jentic

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

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

Key Endpoints

26 endpoints — sendmsg is an all-in-one marketing platform for newsletters providing email automation, landing pages, sms, digital courses and more.

METHOD

PATH

DESCRIPTION

POST

/token

Get authentication token

POST

/ping

Test authentication

POST

/AddUsersOnly

Add or update users

POST

/AddUsersToLists

Add users to mailing lists

GET

/GetUserDetails/{userID}

Get user details

GET

/GetMailingListByID/{listID},{type}

Get mailing list by ID

POST

/GetSystemUsers

Get system users by type

POST

/ChangeUpdateStatus

Change user status

POST

/token

Get authentication token

POST

/ping

Test authentication

POST

/AddUsersOnly

Add or update users

POST

/AddUsersToLists

Add users to mailing lists

GET

/GetUserDetails/{userID}

Get user details

GET

/GetMailingListByID/{listID},{type}

Get mailing list by ID

POST

/GetSystemUsers

Get system users by type

POST

/ChangeUpdateStatus

Change user status

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Sendmsg API by hand means first calling its /token endpoint, then passing the returned token in the Authorization header on every request against gconvertrest.sendmsg.co.il/api/Sendmsg, and handling status codes yourself. Through Jentic you install once, import the Sendmsg API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The Sendmsg API puts the user and list ids in the URL path (/GetUserDetails/{userID} and /GetMailingListByID/{listID}), so a rule can pin your agent to one user or mailing list. You choose the operations it may call, so ones that change state like updating a status are not included unless you add them.

Credential isolation

Your Sendmsg 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.

Intent-based discovery

Agents search Jentic by intent such as 'add users to a mailing list', and Jentic returns the matching Sendmsg operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Sendmsg API through Jentic.

What authentication does the Sendmsg API use?

The Sendmsg API 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 get authentication token with the Sendmsg API?

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

What are the rate limits for the Sendmsg 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 get authentication token through Jentic?

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

How many endpoints does the Sendmsg API have?

The Sendmsg API exposes 26 endpoints covering authentication, users, email campaigns operations.

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

Yes. Because you run Jentic One yourself, you decide which Sendmsg operations your agent may call and which stored credential it uses, so state-changing calls like ChangeUpdateStatus stay off unless you add them. The Sendmsg API carries the user and list ids in the URL path, as in /GetUserDetails/{userID} and /GetMailingListByID/{listID}, so your own rules can pin the agent to a single user or mailing list. This keeps the agent limited to read-only lookups such as GetUserDetails or a specific list while blocking anything you have not explicitly allowed.

Sendmsg API

Name: Sendmsg API
Brand: Sendmsg API
Availability: InStock

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail MarketingapiKey26 EndpointsREST

For Agents

Programmatically get authentication token, test authentication. Covers 26 operations with apiKey authentication.

Use for: I need to authentication token, I want to test authentication, Search for add or update users, Find all add users to mailing lists

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

Sendmsg is an all-in-one marketing platform for newsletters providing email automation, landing pages, SMS, digital courses and more. This API manages mailing lists, newsletters, SMS campaigns, user management, and analytics. The API exposes 26 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

27%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

37%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Sendmsg API to your agent

Capabilities

Start building with Sendmsg API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sendmsg API

Jentic AI Readiness Score

Sendmsg API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness