Handle request errors

  • The Maps Datasets API returns errors with codes, messages, and status information to help you troubleshoot issues.

  • Common errors include missing or expired authentication credentials (401), missing required parameters (400), and invalid dataset IDs (404).

  • Error responses provide details about the cause of the error, such as the missing credential or parameter.

  • Refer to the Google Cloud error documentation for comprehensive information on error handling and troubleshooting.

The Maps Datasets API returns error messages as part of theresponse. For example, if you omit the OAuth token from therequest or if the token has expired, the request returns:

{"error":{"code":401,"message":"Request is missing required authentication credential.    Expected OAuth 2 access token, login cookie or other valid authentication credential.    See https://developers.google.com/identity/sign-in/web/devconsole-project.","status":"UNAUTHENTICATED","details":[{"@type":"type.googleapis.com/google.rpc.ErrorInfo","reason":"CREDENTIALS_MISSING","domain":"googleapis.com","metadata":{"method":"google.maps.mapsplatformdatasets.v1alpha.MapsPlatformDatasetsV1Alpha.ListDatasets","service":"mapsplatformdatasets.googleapis.com"}}]}}

If you omit a required body parameter, such asdisplayName when creating adataset, the request returns:

{"error":{"code":400,"message":"display_name: Display name must be provided","status":"INVALID_ARGUMENT"}}

If you pass an invalid dataset ID, the request returns:

{"error":{"code":404,"message":"Dataset not found","status":"NOT_FOUND"}}

For more information on errors and error handling, seeErrors.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-11-21 UTC.