In the search results, click through to "Stackdriver Monitoring API".
If "API enabled" is displayed, then the API is already enabled. If
not, then click Enable.
gcloud CLI
If you have not already installed the Google Cloud CLI on your
workstation, see
Installing the gcloud CLI.
To see if the Monitoring API is enabled, run the following
command on your workstation, after replacing PROJECT_ID with the
ID of the project for which you want to enable the API:
gcloud services list --project=PROJECT_ID
If monitoring.googleapis.com appears in the output, the API is
enabled.
If the API is not enabled, then run the following command to enable it:
Access to the Monitoring API is controlled by
Identity and Access Management (IAM) roles and permissions.
There is a permission associated with each method, and
permissions for related methods are clustered into roles, which can then
be granted to users. For more information, see
Control access with IAM.
After access to an API is authorized, the API can be used from anywhere.
For example, you can call the timeSeries.list
method from your local workstation. You can also use the API to send
metrics against any entity that can be represented as a monitored resource.
See Monitored-resource types for user-defined metrics
for the list of available types.
You might also be able to use API keys in some situations, but service accounts
are generally recommended. API keys are useful in clients like
browsers and mobile applications that don't have a backend server.
For more information, see Using API Keys.
You can find out more about authentication and authorization
in our Authentication guide.
[[["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-25 UTC."],[],[],null,["# Enable the Monitoring API\n\nThis page describes how to enable and authorize use of the\nMonitoring API v3. You must enable this API before you can use it.\n\nEnable the Monitoring API\n-------------------------\n\nTo determine whether the Monitoring API is enabled or to enable the\nAPI, use either the Google Cloud console or the Google Cloud CLI.\n\n\n### Google Cloud console\n\n1. In the Google Cloud console, select the Google Cloud project for\n which you want to enable the API,\n and then go to the **APIs \\& Services** page:\n\n [Go to **APIs \\& Services**](https://console.cloud.google.com/apis/dashboard)\n2. Click the **Enable APIs and Service** button.\n\n3. Search for \"Monitoring\".\n\n4. In the search results, click through to \"Stackdriver Monitoring API\".\n\n5. If \"API enabled\" is displayed, then the API is already enabled. If\n not, then click **Enable**.\n\n### gcloud CLI\n\n1. If you have not already installed the Google Cloud CLI on your\n workstation, see\n [Installing the gcloud CLI](/sdk/docs/install).\n\n2. To see if the Monitoring API is enabled, run the following\n command on your workstation, after replacing \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e with the\n ID of the project for which you want to enable the API:\n\n gcloud services list --project=\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e\n\n If `monitoring.googleapis.com` appears in the output, the API is\n enabled.\n3. If the API is not enabled, then run the following command to enable it:\n\n gcloud services enable monitoring --project=\u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e\n\n For more information, see\n [`gcloud services`](/sdk/gcloud/reference/services).\n\n\u003cbr /\u003e\n\nAuthorize use of the Monitoring API\n-----------------------------------\n\nAccess to the Monitoring API is controlled by\nIdentity and Access Management (IAM) roles and permissions.\nThere is a permission associated with each method, and\npermissions for related methods are clustered into roles, which can then\nbe granted to users. For more information, see\n[Control access with IAM](/monitoring/access-control).\n\nAfter access to an API is authorized, the API can be used from anywhere.\nFor example, you can call the [`timeSeries.list`](/monitoring/api/ref_v3/rest/v3/projects.timeSeries/list)\nmethod from your local workstation. You can also use the API to send\nmetrics against any entity that can be represented as a monitored resource.\nSee [Monitored-resource types for user-defined metrics](/monitoring/custom-metrics#which-resource)\nfor the list of available types.\n\nIf you are writing an application that uses the\nrecommended [client libraries](/monitoring/docs/reference/libraries), these libraries\nauthorize your application by using\n[Application Default Credentials](/docs/authentication/production).\n\nYou might also be able to use API keys in some situations, but service accounts\nare generally recommended. API keys are useful in clients like\nbrowsers and mobile applications that don't have a backend server.\nFor more information, see [Using API Keys](/docs/authentication/api-keys).\n\nYou can find out more about authentication and authorization\nin our [Authentication guide](/docs/authentication/getting-started)."]]
