To deploy your OpenAPI document, you run the
gcloud endpoints services deploy
command. The first time you deploy your OpenAPI document, the gcloud command
calls a Service Management API to create a managed service by using the name
that you specified in the host field of your OpenAPI document.
Service Management automatically assigns a configuration ID, which
consists of a date stamp followed by a revision number. For example:
2017-02-13r0
If you deploy your service configuration again on the same day,
Service Management increments the revision number in the configuration
ID. If you deploy your service configuration again on another day,
Service Management assigns a new date stamp to the configuration ID and
resets the revision number to 0.
Endpoints uses Service Management to store service
configurations. Service Management stores only the latest 100 service
configurations.
This page describes how to view the name of your service and configuration IDs.
Google Cloud console
In the Google Cloud console, go to the Endpoints > Services page for
your project.
If you have more than one API, select an API from the list.
Click the Deployment history tab.
The service name is displayed between the API name and the tabs,
near the top-left side of the page. In the Service configuration
deployments list, the configuration ID is displayed along with the date and
the email address of the principal who deployed the configuration. The
Service configuration deployments list displays the latest 100
configuration deployments. The most recent configuration is displayed at
the top of the list.
gcloud
Enter the following to display the project IDs for your
Google Cloud projects:
gcloud projects list
Using the applicable project ID from the previous step, set the default
project to the one that your API is in:
gcloud config set project YOUR_PROJECT_ID
Get a list of services in your project:
gcloud endpoints services list
Using the applicable service name from the previous step, get a list of
configuration IDs for the service:
gcloud endpoints configs list --service=YOUR_SERVICE_NAME
For more information on the preceding commands, see the gcloud reference.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eDeploying an OpenAPI document involves using the \u003ccode\u003egcloud endpoints services deploy\u003c/code\u003e command, which creates a managed service via the Service Management API.\u003c/p\u003e\n"],["\u003cp\u003eService Management assigns a configuration ID with a date stamp and revision number each time an OpenAPI document is deployed.\u003c/p\u003e\n"],["\u003cp\u003eRe-deploying the service on the same day increments the configuration ID's revision number, while deploying on a new day resets it and changes the date stamp.\u003c/p\u003e\n"],["\u003cp\u003eEndpoints uses Service Management to manage service configurations, which stores the latest 100 configurations.\u003c/p\u003e\n"]]],[],null,["# Getting the service name and configuration ID\n\nOpenAPI \\| [gRPC](/endpoints/docs/grpc/get-service-name-config-id \"View this page for the Cloud Endpoints gRPC docs\")\n\n\u003cbr /\u003e\n\nTo deploy your OpenAPI document, you run the\n[`gcloud endpoints services deploy`](/sdk/gcloud/reference/endpoints/services/deploy)\ncommand. The first time you deploy your OpenAPI document, the `gcloud` command\ncalls a Service Management API to create a managed service by using the name\nthat you specified in the `host` field of your OpenAPI document.\nService Management automatically assigns a configuration ID, which\nconsists of a date stamp followed by a revision number. For example:\n`2017-02-13r0`\n\nIf you deploy your service configuration again on the same day,\nService Management increments the revision number in the configuration\nID. If you deploy your service configuration again on another day,\nService Management assigns a new date stamp to the configuration ID and\nresets the revision number to 0.\n\nEndpoints uses Service Management to store service\nconfigurations. Service Management stores only the latest 100 service\nconfigurations.\n\nThis page describes how to view the name of your service and configuration IDs.\n\nWhat's next\n-----------\n\n- Learn about [deploying an OpenAPI document](/endpoints/docs/openapi/deploy-endpoints-config).\n- Learn about the [Service Management API](/service-infrastructure/docs/manage-config)."]]
