ApivomApivom
Get Demo

MuleSoft Anypoint Platform API Connector

MuleSoft Anypoint Platform control-plane APIs — Access Management (organisations, business groups, users, connected apps, entitlements), Exchange assets, API Manager instances and policies, CloudHub applications, VPCs and load balancers, Design Center projects, Secrets Manager, Runtime Manager and audit — registered in Apivom Atlas as 254 routes.

What you can do

  • Access Management: organisations and business groups, users and roles, connected applications, entitlements and permissions (92 routes)
  • Exchange: list, read and publish assets, versions, pages and portals (34 routes); Design Center projects and branches (25)
  • API Manager: API instances per environment, policies and automated policies, contracts, tiers, alerts, groups (28 routes)
  • CloudHub and Runtime Manager: applications and domains, Mule versions, VPCs and IPsec, dedicated load balancers, notifications, hybrid servers (46 routes)
  • Secrets Manager (16 routes), audit log queries, Visualizer and monitoring endpoints
  • 254 routes (150 read-only) on anypoint.mulesoft.com, authenticated with a Connected App

Use cases

  • API inventory in the account record — List the API instances, policies and contracts of a customer's environments from API Manager and keep them on the account so architects and sales see the same landscape.
  • Deployment and runtime status at a glance — Read CloudHub applications, their Mule versions and hybrid servers on a schedule to surface outdated runtimes or stopped applications before a review.
  • Governance evidence from the audit log — Query Access Management and audit endpoints for who changed which organisation, user or connected app, and attach the trail to the compliance record.

Anypoint Platform is MuleSoft's control plane for the APIs and integrations an organisation runs: Exchange is where assets are published and discovered, API Manager governs instances and policies per environment, CloudHub and Runtime Manager host and operate the Mule applications, Design Center holds the projects, Secrets Manager the certificates and keys, and Access Management the organisations, business groups, users and connected applications that tie it together. Apivom Atlas catalogues 254 of these control-plane routes, 150 of them read-only, across those surfaces — including the audit log, Visualizer and monitoring endpoints — on anypoint.mulesoft.com. The credential contract is a Connected App of your organisation: the caller obtains the token and sends it as Bearer, Atlas forwards and logs. No Apivom product workflow uses Anypoint Platform today — Apivom's own integrations run on Apivom Atlas rather than on Mule runtimes — so the connector is available to tenants who operate Anypoint and want their API inventory, deployments or audit trail visible from an Apivom workflow, scoped per customer.

Authentication

A Connected App on your Anypoint Platform organisation (client id + secret) with the scopes this API family needs. The caller gets a token at /accounts/api/v2/oauth2/token (client credentials) and sends it as Bearer; Apivom Atlas forwards, logs, stores nothing. Secret encrypted in your Iris tenant.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Which Anypoint control planes does this cover?

The US control plane at anypoint.mulesoft.com. EU and government control planes use different hosts; the connector's allowed host suffix is .mulesoft.com, so a per-request base URL override for eu1.anypoint.mulesoft.com works when your organisation lives there.

Does this call the APIs I built on Mule?

No. These are the platform's own management APIs. Your deployed Mule APIs run on your runtimes with their own hosts and policies; calling them is a separate connector per API.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.