Access to the Error Reporting API is controlled by Identity and Access Management roles and permissions. You can find out more about authentication and authorization for Google Cloud APIs in the Authentication guide.
Data model
The Error Reporting API defines three entities: error events, error groups, and error group stats. The error group stats object is the object that most users will interact with most frequently.
Error events
An ErrorEvent represents a single occurrence of an error in your application. The object contains information about the error, such as the time at which it occurred, the context in which it occurred, and the error message that was returned. An error event is guaranteed to be available for at least 30 days after being generated.
Error groups
ErrorGroup objects are logically-grouped collections of error events. Grouping is based on information in the error event's stack trace. An error group is a simple object containing only the name, group ID, and any associated tracking issues for the group.
To update tracking issues URLs, use this resource's update method.
Error group stats
ErrorGroupStats objects contain detailed information about an error group, and are the API objects that you will interact with most frequently. Information in the groupStats object includes the first and last time an error event in this group occurred, the count, the number of affected users, and more. This object is useful when building widgets and custom dashboards.
Operations
The Error Reporting API supports the following operations:
Report a new error event
List error group stats
List error events
Get error groups
Update an error group's tracking issues
Report error events
You can report error events from your running services by writing them to ReportedErrorEvent. Doing this generates properly formatted error messages in Cloud Logging. The resulting log name is formatted as projects/<PROJECT_ID>/clouderrorreporting.googleapis.com%2Freported_errors. You might incur minor Cloud Logging ingestion costs using this method; to control these costs, review Logs exclusions.
You can also report new error events to Error Reporting by assembling error event entities from your running service and sending them to the events.report method.
List error group stats
To get a list of error group stats, send a request to the groupStats.list method. You can pass one or more query parameters to filter the group stats that are returned.
List error events
To get a list of error events belonging to a specific error group, send a request to the events.list method. You can pass a filter condition to these requests to retrieve only those error events that occurred between a specific start and end time, or those that match specific service contexts.
Get error groups
To retrieve a specific error group resource, send a request to the groups.get method.
Update error groups
To update the tracking issue URLs associated with an error group, send an updated ErrorGroup resource to the groups.update method.
[[["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."],[[["\u003cp\u003eThe Error Reporting API allows you to report errors from your services via a specific endpoint, providing a streamlined way to track and manage application issues.\u003c/p\u003e\n"],["\u003cp\u003eThis API provides read access to organized collections of errors, known as error groups, and to the individual errors within them.\u003c/p\u003e\n"],["\u003cp\u003eError Reporting defines three main entities: error events (single error occurrences), error groups (collections of similar events), and error group stats (detailed information about error groups), with group stats being the object users will interact with most.\u003c/p\u003e\n"],["\u003cp\u003eYou can report error events using either Cloud Logging, which generates properly formatted error messages, or by directly sending error event entities to the \u003ccode\u003eevents.report\u003c/code\u003e method.\u003c/p\u003e\n"],["\u003cp\u003eThe API supports operations for reporting errors, listing error group stats and error events, retrieving error groups, and updating tracking issues for error groups.\u003c/p\u003e\n"]]],[],null,["# Overview\n\nThe Error Reporting API provides:\n\n- A simple [endpoint](/error-reporting/reference/rest/v1beta1/projects.events/report) to **report** errors from your running service.\n- Read access to error groups and their associated errors.\n\n### Getting started\n\n\nEnable the Error Reporting API.\n\n\n[Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=clouderrorreporting.googleapis.com)\n\n\u003cbr /\u003e\n\n### Authorizing use of the API\n\nAccess to the Error Reporting API is controlled by Identity and Access Management roles and permissions. You can find out more about authentication and authorization for Google Cloud APIs in the [Authentication guide](/docs/authentication/getting-started).\n\n\u003cbr /\u003e\n\n| **Note:** API keys are associated with a project for API quota and billing purposes, but they shouldn't be used as an [authentication mechanism](/docs/authentication#authentication_strategies) Instead, use [service accounts](/docs/authentication/getting-started#creating_a_service_account) whenever possible.\n\n\u003cbr /\u003e\n\n### Data model\n\nThe Error Reporting API defines three entities: error events, error groups, and error group stats. The [error group stats](#error-group-stats) object is the object that most users will interact with most frequently.\n\n#### Error events\n\nAn [`ErrorEvent`](/error-reporting/reference/rest/v1beta1/ErrorEvent) represents a single occurrence of an error in your application. The object contains information about the error, such as the time at which it occurred, the context in which it occurred, and the error message that was returned. An error event is guaranteed to be available for at least 30 days after being generated.\n\n#### Error groups\n\n[`ErrorGroup`](/error-reporting/reference/rest/v1beta1/projects.groups#ErrorGroup) objects are logically-grouped collections of error events. Grouping is based on information in the error event's stack trace. An error group is a simple object containing only the name, group ID, and any associated tracking issues for the group.\n\nTo update tracking issues URLs, use this resource's `update` method.\n\n#### Error group stats\n\n[`ErrorGroupStats`](/error-reporting/reference/rest/v1beta1/projects.groupStats/list#ErrorGroupStats) objects contain detailed information about an error group, and are the API objects that you will interact with most frequently. Information in the `groupStats` object includes the first and last time an error event in this group occurred, the count, the number of affected users, and more. This object is useful when building widgets and custom dashboards.\n\n### Operations\n\nThe Error Reporting API supports the following operations:\n\n- Report a new error event\n- List error group stats\n- List error events\n- Get error groups\n- Update an error group's tracking issues\n\n#### Report error events\n\nYou can report error events from your running services by writing them to [`ReportedErrorEvent`](/error-reporting/reference/rest/v1beta1/projects.events/report#ReportedErrorEvent). Doing this generates [properly formatted error messages](/error-reporting/docs/formatting-error-messages) in Cloud Logging. The resulting log name is formatted as `projects/\u003cPROJECT_ID\u003e/clouderrorreporting.googleapis.com%2Freported_errors`. You might incur minor Cloud Logging ingestion costs using this method; to control these costs, review [Logs exclusions](/logging/docs/exclusions).\n\nYou can also report new error events to Error Reporting by assembling [error event entities](/error-reporting/reference/rest/v1beta1/projects.events/report#ReportedErrorEvent) from your running service and sending them to the `events.report` method.\n\n#### List error group stats\n\nTo get a list of error group stats, send a request to the [`groupStats.list`](/error-reporting/reference/rest/v1beta1/projects.groupStats/list) method. You can pass one or more [query parameters](/error-reporting/reference/rest/v1beta1/projects.groupStats/list#body.QUERY_PARAMETERS) to filter the group stats that are returned.\n\n#### List error events\n\nTo get a list of error events belonging to a specific error group, send a request to the [`events.list`](/error-reporting/reference/rest/v1beta1/projects.events/list) method. You can pass a filter condition to these requests to retrieve only those error events that occurred between a specific start and end time, or those that match specific [service contexts](/error-reporting/reference/rest/v1beta1/ServiceContextFilter).\n\n#### Get error groups\n\nTo retrieve a specific error group resource, send a request to the [`groups.get`](/error-reporting/reference/rest/v1beta1/projects.groups/get) method.\n\n#### Update error groups\n\nTo update the tracking issue URLs associated with an error group, send an updated [`ErrorGroup` resource](/error-reporting/reference/rest/v1beta1/projects.groups#ErrorGroup) to the [`groups.update`](/error-reporting/reference/rest/v1beta1/projects.groups/update) method."]]
