Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Per effettuare qualsiasi richiesta all'API Maps Datasets, devi includere:
Il numero o l'ID del tuo progetto Google Cloud nell'intestazione
X-Goog-User-Project della richiesta. Questo valore determina il progetto utilizzato per i calcoli della fatturazione e della quota di utilizzo.
Un token OAuth nell'intestazione Authorization della richiesta. Per saperne di più sull'utilizzo di OAuth con l'API Maps Datasets, consulta Utilizzare OAuth.
Un numero o un ID progetto Google Cloud nell'URL della richiesta. Questo valore
specifica il progetto contenente il set di dati. Anche se questo progetto di solito
è lo stesso specificato nell'intestazione X-Goog-User-Project, non
è obbligatorio che lo sia.
L'ID set di dati nell'URL della richiesta. Ogni volta che esegui un'azione su un
set di dati specifico, trasmetti l'ID del set di dati come parte dell'URL della richiesta.
Puoi includere il comando gcloud direttamente nell'intestazione Authorization di un comando cURL per generare un nuovo token a ogni richiesta, come mostrato nell'esempio precedente.
In alternativa, puoi impostare una variabile di ambiente contenente il token e poi
passare la variabile di ambiente come parte della richiesta:
[null,null,["Ultimo aggiornamento 2025-09-03 UTC."],[[["\u003cp\u003eAll Maps Datasets API requests require a Google Cloud project number or ID for billing and usage quota, specified in the \u003ccode\u003eX-Goog-User-Project\u003c/code\u003e header or using a service account.\u003c/p\u003e\n"],["\u003cp\u003eAn OAuth token is necessary for authentication and should be included in the \u003ccode\u003eAuthorization\u003c/code\u003e header of each request.\u003c/p\u003e\n"],["\u003cp\u003eThe request URL must contain the Google Cloud project number or ID and the dataset ID to specify the location of the dataset.\u003c/p\u003e\n"],["\u003cp\u003eAdditional parameters may be required for certain requests, as detailed in the specific request documentation.\u003c/p\u003e\n"],["\u003cp\u003eYou can obtain your Google Cloud project number or ID from the project's Overview page in the Cloud Console and generate an OAuth token using the \u003ccode\u003egcloud\u003c/code\u003e command.\u003c/p\u003e\n"]]],["To interact with the Maps Datasets API, requests must include: the Google Cloud project number or ID in the `X-Goog-User-Project` header for billing and quota (unless using a service account); an OAuth token in the `Authorization` header; the project number or ID in the URL; and the dataset ID in the URL. The project number and ID can be found on the project's overview page. An OAuth token can be generated using the `gcloud auth application-default print-access-token` command.\n"],null,["# Required request parameters\n\nTo make any request to Maps Datasets API, you must include:\n\n- The number or ID of your Google Cloud project in the\n `X-Goog-User-Project` header of the request. This value determines the\n project used for billing and usage quota calculations.\n\n | **Note:** If you are using a service account for authentication, you can omit the `X-Goog-User-Project` header. For more information about service accounts, see [Authentication at Google](https://cloud.google.com/docs/authentication).\n- An OAuth token in the `Authorization` header of the request. For more\n information about using OAuth with Maps Datasets API, see\n [Use OAuth](/maps/documentation/datasets/oauth-token).\n\n- A Google Cloud project number or ID in the request URL. This value\n specifies the project containing the dataset. While this project is usually\n the same as the project specified in the `X-Goog-User-Project` header, it\n is not required to be the same.\n\n- The dataset ID in the request URL. Whenever you perform an action on a\n specific dataset, you pass the ID of the dataset as part of the request URL.\n\n| **Note:** Some requests require additional parameters that are described in the documentation on those requests.\n\nFor example, to delete a dataset: \n\n```\ncurl -X DELETE \\\n-H 'X-Goog-User-Project: \u003cvar translate=\"no\"\u003ePROJECT_NUMBER_OR_ID\u003c/var\u003e' \\\n-H \"Authorization: Bearer $(gcloud auth application-default print-access-token)\" \\\nhttps://mapsplatformdatasets.googleapis.com/v1/projects/PROJECT_NUMBER_OR_ID/datasets/DATASET_ID\n```\n\nGet the project number\n----------------------\n\nTo get the \u003cvar translate=\"no\"\u003ePROJECT_NUMBER_OR_ID\u003c/var\u003e of your Google Cloud project:\n\n1. Go to the project's\n [Overview page](https://console.cloud.google.com/home/dashboard)\n in the Cloud console.\n\n2. If prompted, select your project.\n\n3. The **Project number** and **Project ID** appear in the **Project info**\n area of the overview screen.\n\nGet an OAuth token\n------------------\n\n| **Note:** The procedure below to generate an OAuth token is not intended for use in a production environment. Use this procedure for a development or testing environment only.\n\nFor authentication, your API request must contain an OAuth token in the\n`Authorization` header. For more, see [Use OAuth](/maps/documentation/datasets/oauth-token).\n\nFor example, use the following `gcloud` command to generate the token: \n\n```\ngcloud auth application-default print-access-token\n```\n\nYou can include the `gcloud` command directly in the `Authorization` header in a\ncURL command to generate a new token on each request, as shown in the example\nabove.\n\nAlternatively, you can set an environment variable containing the token and then\npass the environment variable as part of the request: \n\n export TOKEN=$(gcloud auth application-default print-access-token)\n curl -X DELETE \\\n -H 'X-Goog-User-Project: \u003cvar translate=\"no\"\u003ePROJECT_NUMBER_OR_ID\u003c/var\u003e' \\\n -H \"Authorization: Bearer $TOKEN\" \\\n https://mapsplatformdatasets.googleapis.com/v1/projects/\u003cvar translate=\"no\"\u003ePROJECT_NUMBER_OR_ID\u003c/var\u003e/datasets/\u003cvar translate=\"no\"\u003eDATASET_ID\u003c/var\u003e"]]
