canonical: https://jentic.com/apis/mobimag.app/mobimag-app # Mobimag App Mobimag Contacts API 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. ## For AI agents Authenticate a Mobimag publisher and manage subscriber contacts and publications via 4 cloud-function endpoints. ## Scope Does not handle email delivery, payment processing, or content publishing - use for Mobimag publisher authentication and subscriber contact management only. ## Capabilities - 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 - Scope subscriber operations to a specific user via the X-EMAIL header ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'create a Mobimag contact', load the /create schema, and execute it with the new subscriber's email. ## Key endpoints | 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 | ## Key resources - **Authentication** — Authenticate a publisher with X-API-KEY and X-EMAIL headers - **Publications** — List the magazine publications belonging to the publisher - **Contacts** — List existing subscriber contacts and create new contact records ## Why Jentic - **Setup:** Wiring the Mobimag Contacts API by hand means handling its API key auth, running the publisher /auth step, and mapping subscriber list and create calls yourself. Through Jentic you install once, import the Mobimag Contacts API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Mobimag's publisher and contact targets travel in the request body rather than the URL path, so scope your agent by limiting it to the operations it needs, such as listing publications and reading the contact list. You leave out contact creation so the agent reads subscriber data without adding new contacts. - **Credential handling:** Your Mobimag API key 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. - **Discovery method:** Agents search Jentic by intent such as 'list Mobimag publications' or 'read the subscriber contact list', and Jentic returns the matching Mobimag operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Mobimag API** — Twin Mobimag spec covering the same contacts and publications surface - **SendGrid Mail API** — Send transactional and digest emails to Mobimag subscribers - **Mailchimp Marketing API** — Run marketing campaigns to a synced Mobimag subscriber list ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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 your Jentic One instance 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 One, the self-hosted execution layer. ### Can I limit what my agent is allowed to do with the Mobimag Contacts API? Yes. Because you run Jentic One yourself, your own rules decide which of the four Mobimag operations the agent may call and which credentials it may use. You can allow read-only access by scoping the agent to GET /publications and GET /list while leaving out POST /create, so it can read publications and the subscriber contact list without adding new contacts. Since Mobimag's publisher and contact targets travel in the request body rather than the URL, operation-level scoping is how you keep the agent inside its intended boundary.