Mobimag Contacts API

Name: Mobimag Contacts API API
Brand: Mobimag Contacts API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey4 EndpointsREST

For Agents

Authenticate a Mobimag publisher and manage subscriber contacts and publications via 4 cloud-function endpoints.

Connect the Mobimag Contacts API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Mobimag Contacts API API.

Authenticate a Mobimag publisher via the /auth endpoint using X-API-KEY and X-EMAIL headers

List the publications available under the authenticated publisher with /publications

Retrieve the contact list for a publisher's subscribers via /list

Create a new subscriber contact record through /create

GET STARTED

Start building with Mobimag Contacts API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Mobimag Contacts API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Mobimag Contacts API, keeping it validated and agent-ready. Mobimag is a digital magazine publishing platform that lets publishers manage subscriber contacts and the publications those contacts can access. The Contacts API exposes four endpoints for authenticating a publisher, listing publications, listing existing contacts, and creating new contact records, deployed as a Google Cloud Function under us-central1-mobimagprod.cloudfunctions.net/contacts. Authentication uses two API key headers: X-API-KEY for the publisher and X-EMAIL to scope the request to a specific user identity.

Use Cases

Patterns agents use Mobimag Contacts API API for, with concrete tasks.

★ Subscriber import for a digital magazine

Publishers migrating an existing reader list onto Mobimag iterate over their export and POST each row to /create with the X-API-KEY header for the publisher and the X-EMAIL header for the reader. The minimal four-endpoint surface keeps the integration simple and deployable as a one-off migration script.

Iterate over a CSV of subscriber emails and POST each one to /create with X-API-KEY for the publisher and X-EMAIL set to the subscriber's address.

Publication catalog lookup

Front-end clients call /publications to render the catalogue of magazines available under the authenticated publisher, then use /list to show which contacts have access. This pattern keeps publisher-side logic out of the client and lets the cloud function enforce the X-API-KEY scope server-side.

GET /publications with the publisher's X-API-KEY, render the returned titles, then GET /list to fetch the associated contacts.

Agent integration via Jentic

An AI assistant for a Mobimag publisher can search Jentic for 'create a Mobimag contact', load the /create operation schema, and execute the call without exposing the X-API-KEY. The agent can chain into /publications and /list to give a full picture of catalogue and subscribers in a single conversation.

Search Jentic for 'create a Mobimag contact', load the /create schema, and execute it with the new subscriber's email.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/auth

Authenticate a Mobimag publisher

GET

/publications

List publisher publications

GET

/list

List subscriber contacts

POST

/create

Create a new subscriber contact

POST

/auth

Authenticate a Mobimag publisher

GET

/publications

List publisher publications

GET

/list

List subscriber contacts

POST

/create

Create a new subscriber contact

Why though Jentic?

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

Credential isolation

Mobimag X-API-KEY and X-EMAIL header values are stored in the Jentic MAXsystem vault. Agents never see the keys directly; Jentic injects both headers when executing /auth, /publications, /list, or /create.

Intent-based discovery

Agents search Jentic for 'create a Mobimag contact' or 'list Mobimag publications' and Jentic returns the matching cloud-function endpoint with its input schema, so the agent does not need to read a Postman collection.

Time to first call

Direct Mobimag integration: half a day to wire the four endpoints and dual-header auth. Through Jentic: under 30 minutes once the publisher key is vaulted.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mobimag API

Twin Mobimag spec covering the same contacts and publications surface

Use mobimag.com/main when callers reference the .com domain; use mobimag.app/contacts-api when they reference the .app domain. Both target the same backend.

Complementary

SendGrid Mail API

Send transactional and digest emails to Mobimag subscribers

Pair SendGrid with Mobimag when the publisher needs to email contacts pulled from /list — Mobimag does not deliver email itself.

Complementary

Mailchimp Marketing API

Run marketing campaigns to a synced Mobimag subscriber list

Use Mailchimp alongside Mobimag when the publisher wants newsletter campaigns and segmentation on top of the Mobimag subscriber list.

FAQs

Specific to using Mobimag Contacts API API through Jentic.

Why is there no official OpenAPI spec for Mobimag Contacts API?

Mobimag does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mobimag Contacts 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 Mobimag Contacts API use?

The API uses two apiKey headers: X-API-KEY identifies the publisher and X-EMAIL scopes the request to a specific user identity. Through Jentic both header values are stored in the MAXsystem vault and injected at execution time.

Can I list all publications for a Mobimag publisher?

Yes. Call GET /publications with the publisher's X-API-KEY. The endpoint returns the publications attached to that publisher account, which you can then cross-reference against the contacts returned by /list.

What are the rate limits for the Mobimag Contacts API?

The OpenAPI specification does not declare rate limits, and Mobimag does not publish them. Treat HTTP 429 responses as the back-off signal and contact Mobimag if you plan a large bulk import.

How do I create a Mobimag subscriber contact through Jentic?

Run pip install jentic, search Jentic for 'create a Mobimag contact', load the /create schema, and execute it with the new subscriber's email. Jentic injects the X-API-KEY and X-EMAIL headers from the vault.

Is the Mobimag Contacts API free to use?

Mobimag is a commercial digital magazine platform; API access is gated by publisher accounts on Mobimag. There is no public free tier. Get started with Jentic at https://app.jentic.com/sign-up.