API resources overview

This page applies to Apigee and Apigee hybrid.

In API hub, every registered API is represented as an API resource. It serves as a comprehensive, centralized record that captures all metadata, specifications, and usage information about your API. Using API resources, you can efficiently manage and govern your entire API portfolio.

An API resource is composed of several key concepts:

  • API version: A version represents the state of an API at a specific point in time. An API can have multiple versions, allowing you to track its evolution and manage different releases independently. See Versions overview for more details.
  • Specifications: Each API version can have one or more specification files attached to it. A specification is a machine-readable document that describes the interface of your API. API hub supports various specification types, including:
    • OpenAPI for REST APIs
    • gRPC proto files for gRPC APIs
    • MCP schema for Model Context Protocol (MCP) APIs

    For more information about specifications, see Specifications overview.

  • API operations and MCP tools: These are the individual functions or capabilities represented as distinct entities of your API. API operations are of two types:
    1. HTTP operations: exposed as operations for API styles like REST and SOAP.
    2. MCP tools: exposed as tools for MCP APIs, which are designed for AI agents.

    For more information about API operations and MCP tools, see API operations and MCP tools.

  • API deployments: A deployment represents a location where a specific version of your API is running. This allows you to track where your APIs are deployed and how they are being used across different environments. See Deployments overview for more details.
  • API attributes: Attributes are key-value pairs that you can use to add descriptive information to your API resources. This metadata helps with organization, discovery, and governance. API hub supports two types of attributes:
    • System attributes: These are predefined attributes provided by API hub, such as API style, Target users, and Maturity level
    • Additional attributes: These are custom attributes that you can create to meet your organization's specific needs.

    For more information about adding and managing attributes, see Manage attributes.

What's next