Compare Classic APIM with APIM 3.0

Classic APIM and APIM 3.0 support the same API implementation approaches, but they differ in how efficiently those APIs can be governed, reused, and scaled. APIM 3.0 modernizes the platform with reusability, composability, and an updated user interface, enabling you to grow API programs without increasing complexity.

Similarities

Classic APIM and APIM 3.0 have a common foundation. The intentional continuity enables you to evolve API management without changing the underlying implementation models. Both Classic APIM and APIM 3.0 support:

  • APIs implemented as proxies in front of third-party or external endpoints.
  • Native SnapLogic task APIs that execute pipelines on the SnapLogic infrastructure.
  • The same policy hierarchy:
    Classic APIM APIM 3.0
    Org/Environment level - applies to all API/Proxy versions unless overridden at a version or endpoint level Catalog Policy - applies to all Services unless overridden at a version or endpoint level
    API or Proxy version - applies unless overridden at the endpoint level Service version - applies unless overridden at the endpoint level
    API sub-version or Proxy endpoint Service endpoint
  • Governance controls such as authentication, authorization, rate limiting, and traffic management.
  • A developer portal to publish APIs for consumption.

Differences

The primary difference between Classic APIM and APIM 3.0 is not the API implementation model, but how APIs and governance are modeled, reused, and operated.

Classic APIM:

  • Supports two types of APIs:
    • Proxies that front third-party or external endpoints.
    • Native SnapLogic APIs, implemented and executed by Snaplexes.
  • APIs are managed individually, regardless of implementation type, and can't be combined.
  • Policies support governance, but are typically:
    • Defined per API or API version.
    • Copied and customized rather than reused.
  • Configuration grows linearly with the number of APIs.
  • The user interface reflects older design patterns and workflows.

APIM 3.0:

  • Designed explicitly for domain-driven Services, composability, and reuse.
  • Like Classic APIM, APIM 3.0 supports proxies and native SnapLogic APIs modeled as Services. A single Service can support multiple endpoints.
  • Reusable Policies composed of individual rules provide governance.
  • The modernized user interface lets you define common patterns once and apply them consistently.

The following table summarizes these differences by feature area.

Feature Classic APIM APIM 3.0
API support Proxies to third-party/external endpoints and native SnapLogic APIs Proxies to third-party/external endpoints and native SnapLogic APIs modeled as Services that can support multiple endpoints
Governance support Through individual Policies Through Policies composed of individual rules. Rules are the equivalent of Classic APIM Policies.
Governance reuse Limited / manual First-class reusable assets
Reusability model Minimal Core design principle
Composability Limited Explicitly supported
User interface Legacy Modern
Scalability model Configuration per API Shared, reusable building blocks

Guidance for Classic APIM customers

  • If you are maintaining existing APIs and Proxies or working in the Classic interface, refer to the Classic APIM documentation.
  • If you are building new APIs, standardizing governance, or expanding an API program across teams or domains, APIM 3.0 provides better reuse, consistency, and usability.
  • To take advantage of APIM 3.0 benefits, SnapLogic provides an automated Migration Tool.
  • Always confirm that the documentation corresponds with the product you are using: