> Documentation index for AI agents: https://docs.pagerduty.com/llms.txt

# Events API v2

# PagerDuty Events API V2

The Events API V2 enables you to add PagerDuty's advanced event and incident management functionality to any system that can make an HTTP API call.

## Description

The API is designed to allow you to easily integrate a monitoring system with PagerDuty. Monitoring systems generally send out events when problems are detected and when these problems have been resolved (fixed). Certain systems also understand the concept of acknowledgements: problems can be acknowledged by a person to signal that they are working on fixing the issue.

The Events API V2 is a highly reliable, highly available asynchronous API that ingests events from monitoring tools. Events sent via the API are routed to a PagerDuty service and processed. They may result in a new alert and/or incident being created, or an existing one being updated or resolved.

Previously, the Events API V2 was also used to integrate PagerDuty with ticketing systems and various other software tools. As of 2017, we now recommend using our new synchronous Incidents API to integrate ticketing systems or other systems of record.

Interested in becoming a PagerDuty partner? Check out how you can [Publish an App](https://docs.pagerduty.com/developer/publish-an-app)!


## Getting Started

The Events API V2 can be used with any Events API V2 Integration in PagerDuty.

## Making a Request

To make an API request, POST a JSON object of the desired event type to the following URL:

* https://events.pagerduty.com/v2/enqueue

## API Response Codes & Retry Logic

Ideally, the API request will succeed and the PagerDuty server will indicate that it successfully received that event. In practice, the request may fail due to various reasons.

The following table shows the possible results of the API request and if you need to retry the API call for that result:


| Result  | Description   | Retry? |
| ------- | ------------- | ------ |
| 202     | Accepted - The event has been accepted by PagerDuty. See below for details. | No |
| 400     | Bad Request - Check that the JSON is valid. See below for details.    | No |
| 429     | Too many API calls at a time.                             | Yes - retry after some time. |
| 500 or other 5XX  | Internal Server Error - the PagerDuty server experienced an error while processing the event. | Yes - retry after some time. |
| Networking Error  | Error while trying to communicate with PagerDuty servers.   | Yes - retry after some time. |


## API Limits

There is a limit on the number of events that a service can accept at any given time. Depending on the behavior of the incoming traffic and how many incidents are being created at once, we dynamically adjust our throttle limits.

If each of the events your monitoring system is sending is important, be sure to retry on a 429 response code, preferably with a back off.

- [Send Event](https://docs.pagerduty.com/developer/api/reference/events-v2/send-event.md)
- [Send Change Event](https://docs.pagerduty.com/developer/api/reference/events-v2/send-change-event.md)

## Developer Agreement

Your access to and use of the PagerDuty Developer Services is governed by the [PagerDuty Developer Agreement](https://docs.pagerduty.com/developer/pagerduty-developer-agreement).