[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[[["\u003cp\u003eThis page focuses on API resources within Apigee and Apigee hybrid, representing registered APIs in API Hub.\u003c/p\u003e\n"],["\u003cp\u003eAn API resource is a complex entity that can have multiple versions, each with its own set of associated entities like operations, deployments, and API specifications.\u003c/p\u003e\n"],["\u003cp\u003eAPI resources can be enriched with attributes that describe them, which include both system-defined and user-defined types.\u003c/p\u003e\n"],["\u003cp\u003eSystem-defined attributes for an API include details like its style (REST, gRPC, etc.), target users, responsible team, business unit, and maturity level.\u003c/p\u003e\n"]]],[],null,["# API resources overview\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\nWhen you register an API with API hub, you create and store an entity that represents the API. We call\nthis entity an **API resource**. API resources stored in API hub are searchable and provide detailed\noperational and descriptive information about the API.\n\nAn API resource is a complex entity that can have one or more versions associated with it.\nYou can think of a version as the state of an API at a point in time. Each version can have\nits own set of entities such as [operations parsed from an API specification](./specs-intro#specificationparsing), [deployments](/apigee/docs/apihub/deployments-intro),\nand [API specifications](/apigee/docs/apihub/specs-intro), as shown in Figure 1.\n\n**Figure 1.** An API can have multiple versions.\n\nEither at the time you register an API or afterwards,\nyou can add and edit API resource attributes to build\na rich description of the API. See [Manage attributes](./manage-attributes).\n\nAPI hub supports both system-defined and user-defined attributes. Examples of system defined attributes include:\n\n- **API style**: An attribute with default values of REST, gRPC, SOAP, and Async API.\n- **Target users**: The intended users (consumers) of an API\n- **Team**: The producing team or teams responsible for an API\n- **Business unit**: The business unit responsible for an API\n- **Maturity level**: An indication of the API's lifecycle stage\n\nFinally, an API resource can have [user-defined attributes](./manage-attributes#user-attributes), which you define in Settings based on your\norganizational or team needs."]]
