Mindbaz API

Name: Mindbaz API
Brand: Mindbaz API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingEmail MarketingapiKey30 EndpointsREST

For Agents

Manage subscribers, custom fields, imports, exports, advertisements, and subscriptions inside a Mindbaz email marketing site via API key authentication.

Install Jentic One Beta

Connect the Mindbaz API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mindbaz 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://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 Mindbaz API.

Export subscribers to an SFTP repository for downstream warehouse loads

Import subscribers in bulk to onboard a new list into Mindbaz

Manage custom subscriber fields and the field quota that bounds the data model

GET STARTED

Start building with Mindbaz API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Mindbaz API for, with concrete tasks.

★ Warehouse Sync via Subscriber Export

An agent kicks off a subscribers export to an SFTP repository, monitors the export state, and triggers a downstream warehouse load when the file lands. Mindbaz becomes a first-class source in a marketing data pipeline without manual file handling.

POST /exports/subscribers to start an export, then poll GET /exports/subscribers/{idExport} until status is complete and notify a downstream loader.

Bulk Subscriber Onboarding

When a new list arrives from an acquisition or partner, an agent runs a Mindbaz import to load it into the platform. Operators avoid one-by-one subscriber API calls and the new audience is ready for campaigns within minutes.

Run an import job via the imports endpoint with a CSV of new subscribers and verify completion through the export/import status endpoints.

Field Schema Management

Marketing ops adds or updates custom subscriber fields (e.g. preferred language, plan tier) so segmentation works correctly. The API exposes the field list, the field quota, and an update endpoint so the schema is managed alongside the rest of the marketing stack.

Call GET /fields/list and GET /fields/quota to inventory current fields, then PUT /Fields to update a field's properties.

Agent-Driven Email Marketing via Jentic

Through Jentic, an agent triggers Mindbaz exports, imports, and field updates by intent rather than manual API plumbing. The Mindbaz API key is held in the Jentic vault and the per-site idsite is included in the path, so an agent can run multi-site marketing operations without ever holding a credential.

Use Jentic search 'export subscribers from mindbaz', load the schema for POST /exports/subscribers, and execute with the target SFTP repository.

Key Endpoints

30 endpoints — jentic publishes the only available openapi specification for mindbaz api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/exports/subscribers

Export subscribers to SFTP

GET

/exports/subscribers/{idExport}

Get export job info

GET

/exports/repositories

List configured SFTP repositories

GET

/fields/list

List subscriber fields

GET

/fields/quota

Get the field quota for the site

PUT

/Fields

Update a custom field

POST

/exports/subscribers

Export subscribers to SFTP

GET

/exports/subscribers/{idExport}

Get export job info

GET

/exports/repositories

List configured SFTP repositories

GET

/fields/list

List subscriber fields

GET

/fields/quota

Get the field quota for the site

Why Jentic?

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

Credential isolation

Mindbaz API keys are stored encrypted in the Jentic vault (MAXsystem) and injected into the Authorization header at execution time. The raw key never enters the agent's context, and the per-site idsite is supplied as a path parameter at call time.

Intent-based discovery

Agents search by intent (e.g., 'export subscribers from mindbaz') and Jentic returns the matching Mindbaz operation with its input schema, so the agent calls POST /exports/subscribers without browsing learn.mindbaz.com.

Time to first call

Direct Mindbaz integration: 1-2 days to model the per-site authentication, SFTP repositories, and async export polling. Through Jentic: under an hour — search, load schema, execute.

FAQs

Specific to using Mindbaz API through Jentic.

Why is there no official OpenAPI spec for Mindbaz API?

Mindbaz does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mindbaz API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Mindbaz API use?

The API uses an API key sent in the Authorization header (the apiKey security scheme). Each request is also scoped to a Mindbaz site via the {idsite} path parameter. Through Jentic, the key sits in the encrypted vault and is injected per request without entering the agent's context.

Can I export subscribers to an SFTP server through the API?

Yes. POST /exports/subscribers triggers an export to a configured SFTP repository, and GET /exports/subscribers/{idExport} reports the export's status, which is the supported flow for warehouse sync jobs.

What are the rate limits for the Mindbaz API?

Mindbaz documents per-site limits in their developer portal at learn.mindbaz.com. Treat the API as rate-limited per key and per site, and back off on HTTP 429 responses.

How do I export subscribers to SFTP through Jentic?

Run pip install jentic, search for 'export subscribers from mindbaz', load the schema for POST /exports/subscribers, and execute with the target SFTP repository id. Jentic injects your stored Authorization header automatically.

How is the field quota enforced?

GET /fields/quota returns the current number of subscriber fields used and the maximum allowed for the site, which is documented per Mindbaz contract; field creation will be rejected once that maximum is reached.