[[["์ดํดํ๊ธฐ ์ฌ์","easyToUnderstand","thumb-up"],["๋ฌธ์ ๊ฐ ํด๊ฒฐ๋จ","solvedMyProblem","thumb-up"],["๊ธฐํ","otherUp","thumb-up"]],[["์ดํดํ๊ธฐ ์ด๋ ค์","hardToUnderstand","thumb-down"],["์๋ชป๋ ์ ๋ณด ๋๋ ์ํ ์ฝ๋","incorrectInformationOrSampleCode","thumb-down"],["ํ์ํ ์ ๋ณด/์ํ์ด ์์","missingTheInformationSamplesINeed","thumb-down"],["๋ฒ์ญ ๋ฌธ์ ","translationIssue","thumb-down"],["๊ธฐํ","otherDown","thumb-down"]],["์ต์ข ์ ๋ฐ์ดํธ: 2025-09-03(UTC)"],[[["\u003cp\u003eAPI hub utilizes versions to represent the state of an API at a specific point in time, allowing for the organization of APIs based on operations, deployments, and attributes.\u003c/p\u003e\n"],["\u003cp\u003eA version in API hub is a logical grouping of APIs, usually centered around the operations an API can perform, such as adding, finding, and deleting a pet in a Pet Store API example.\u003c/p\u003e\n"],["\u003cp\u003eAPI hub allows the addition of OpenAPI specifications to an API version, from which it will automatically extract information, although versions can also be created manually and populated with relevant information.\u003c/p\u003e\n"],["\u003cp\u003eNew versions of an API may be created when new operations are added or when there are backwardly incompatible changes, particularly if the changes are associated with new deployments.\u003c/p\u003e\n"],["\u003cp\u003eEach API version has system attributes like Lifecycle, Compliance, Accreditation, and Documentation, which can be customized, and users can also define their own custom attributes for each version.\u003c/p\u003e\n"]]],[],null,["# Versions overview\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\nThis topic\nexplains what you need to know about creating and managing versions in API hub.\n\nWhat is a version?\n------------------\n\n\nEvery API resource in API hub has at least one version associated with it. You can think of a\nversion as the state of an API at a point in time. Fundamentally, versions help you group and\norganize your APIs based on underlying sets of operations, deployments, specifications, and other attributes, as shown\nin Figure 1.\n\n**Figure 1.** Each version can have operations, deployments, and other attributes.\n\n\nIn API hub, a version represents a logical grouping of APIs. Usually, but not necessarily, this\ngrouping revolves around the operations an API can perform. For example, let's say you have\na Pet Store API, and the first version of this API lets you perform basic tasks, like adding\na pet, finding a pet, and deleting a pet from the store. These are examples of operations.\n\nIt's a good practice for a version to include a set of API operations that are deployed\ntogether. For example, a pet store API might have a version that includes add, find, and\ndelete operations, all deployed to the same environments.\n\nAnother good way to think about a version is that it\nrepresents the API producer's view of the API. It's the collection of features and\ncapabilities that the people who built the API put into it and *expect to be deployed\nwith it*.\n\nCreating versions\n-----------------\n\n\nSuppose the details of an API you want to add to API hub are captured in an OpenAPI spec.\nIf so, you can [add the spec\nto an API version](./manage-specifications#addspec). When you do, API hub parses\nthe spec and pulls information out of it, such as which operations the API includes, and stores that\ninformation with the version. If you don't have an OpenAPI spec, you can still [create a version](./manage-versions#addversion), but you'll have\nto populate it manually with relevant descriptive information. One other case where API hub\nsupports parsing of API details through the [auto-registration of Apigee API proxies](./auto-register-apigee-proxies).\n| **Note:**API hub only supports the parsing of OpenAPI specs.\n\n\nโYou can upload multiple API specification files to the same version.\n| **Note:**API hub cannot guarantee the stability of an API provided by an API producer. API hub assumes that all operations contained in an API version are intended to be deployed together.\n\n### When to create a new version?\n\n\nIf new operations are added to an API, it may warrant creating a new version, or\nperhaps not.\n\n\nLet's say the API producer adds a new operation to an API and intends it to be deployed to all\nof the deployments currently associated with the version. In that case, the producer may choose\nnot to create a new version of the API. On the other hand, if the producer makes a backwardly\nincompatible change (a breaking change) and chooses to associate it with a new deployment,\nyou may wish to create a new version.\n\n\nYou can see that API hub provides flexibility for you to define and organize your API versions\nto best suit your organization's needs and the needs of specific API producers.\n\nSystem attributes\n-----------------\n\nVersions include the following system attributes by default. You can modify the values associated\nwith these attributes in Settings. For details, see [Manage attributes](./manage-attributes).\n\nUser-defined attributes\n-----------------------\n\nDepending on your team or organizational needs, you can define custom attributes (name/value pairs)\nfor versions. See [Manage attributes](/apigee/docs/apihub/manage-attributes)."]]
