Install Jentic One Beta

Connect the Sendspark API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sendspark 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%2Fsendspark.com%2Fsendspark" | 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%2Fsendspark.com%2Fsendspark" | 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 Sendspark API.

API health status

Create dynamic video campaign

List dynamic video campaigns

Get dynamic campaign by ID

Add single prospect to campaign

Use Cases

GET STARTED

Start building with Sendspark API

Explore with Jentic One

View OpenAPI Document

Automated Dynamic Campaigns Management

Automate dynamic campaigns operations by combining multiple Sendspark API endpoints. Agents can create dynamic video campaign and then list dynamic video campaigns in a single workflow.

Call POST /v1/workspaces/{workspaceId}/dynamics to create dynamic video campaign, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sendspark 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 'API health status', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — api for creating and managing dynamic video campaigns and prospects in sendspark.

METHOD

PATH

DESCRIPTION

GET

/v1/auth/health

API health status

POST

/v1/workspaces/{workspaceId}/dynamics

Create dynamic video campaign

GET

/v1/workspaces/{workspaceId}/dynamics

List dynamic video campaigns

GET

/v1/workspaces/{workspaceId}/dynamics/{dynamicId}

Get dynamic campaign by ID

GET

/v1/workspaces/{workspaceId}/dynamics/{dynamicId}/prospects/{email}

Get prospect by email

POST

/v1/workspaces/{workspaceId}/dynamics/{dynamicId}/prospect

Add single prospect to campaign

POST

/v1/workspaces/{workspaceId}/dynamics/{dynamicsId}/prospects/bulk

Add multiple prospects in bulk

GET

/v1/auth/health

API health status

POST

/v1/workspaces/{workspaceId}/dynamics

Create dynamic video campaign

GET

/v1/workspaces/{workspaceId}/dynamics

List dynamic video campaigns

GET

/v1/workspaces/{workspaceId}/dynamics/{dynamicId}

Get dynamic campaign by ID

GET

/v1/workspaces/{workspaceId}/dynamics/{dynamicId}/prospects/{email}

Get prospect by email

POST

/v1/workspaces/{workspaceId}/dynamics/{dynamicId}/prospect

Add single prospect to campaign

POST

/v1/workspaces/{workspaceId}/dynamics/{dynamicsId}/prospects/bulk

Add multiple prospects in bulk

Why Jentic?

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

Setup

Wiring Sendspark by hand means sending both the x-api-key and x-api-secret headers on every request and carrying the workspace id through each call yourself. Through Jentic you install once, import Sendspark from the API Directory, store the key and secret once, and your agent calls it.

Permission scoping

Sendspark puts the workspace and dynamic ids in the URL path (/v1/workspaces/{workspaceId}/dynamics/{dynamicId}/...), so a rule can pin your agent to one workspace: it can add prospects to that workspace's dynamics and nothing else. You choose the operations it may call, so bulk prospect creation is not included unless you add it.

Credential isolation

Your Sendspark key and secret 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.

Intent-based discovery

Agents search Jentic by intent such as 'list dynamics in a workspace' or 'add a prospect', and Jentic returns the matching Sendspark operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Sendspark API through Jentic.

What authentication does the Sendspark API use?

The Sendspark API uses an API key passed in the `x-api-key` 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 API health status with the Sendspark API?

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

What are the rate limits for the Sendspark 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 API health status through Jentic?

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

How many endpoints does the Sendspark API have?

The Sendspark API exposes 7 endpoints covering dynamic campaigns, health, prospects operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sendspark operations and credentials the agent may use. Since Sendspark carries the workspace and dynamic ids in the URL path, such as /v1/workspaces/{workspaceId}/dynamics/{dynamicId}, you can pin the agent to a single workspace so it only adds prospects to that workspace's dynamic campaigns. You also choose the specific operations it may call, so it can list dynamics and add a single prospect while bulk prospect creation stays off unless you grant it.

Sendspark API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingEmail MarketingapiKey7 EndpointsREST

For Agents

Programmatically API health status, create dynamic video campaign. Covers 7 operations with apiKey authentication.

Use for: I need to API health status, I want to dynamic video campaign, Search for dynamic video campaigns, Find all dynamic campaign by id

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

API for creating and managing dynamic video campaigns and prospects in Sendspark. The API exposes 7 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

100%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: D+Signals: 4

35%

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.

54%

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Sendspark API to your agent

Capabilities

Use Cases

Start building with Sendspark API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sendspark API

Jentic AI Readiness Score

Sendspark 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