api-schema icon indicating copy to clipboard operation
api-schema copied to clipboard

PagerDuty OpenAPI schemas

Results 33 api-schema issues
Sort by recently updated
recently updated
newest added

In the [api documentation for listing all Schedules](https://developer.pagerduty.com/api-reference/846ecf84402bb-list-schedules), it shows the `overrides_subschedule` and `final_schedule` as returned response data. However, these don't seem accessible from this endpoint. I was able to...

I have yet to find terraform support for the integration-jira-service suite of APIs. Are there plans to provide this? This seems primed and ready to be incorporated into the existing...

Hi there. I'm trying to generate a sdk for the REST API in kotlin. Following the instructions on https://github.com/OpenAPITools/openapi-generator, I'm running the following command to do so. ``` openapi-generator generate...

bug

Using the [apitools.dev online swagger parser](https://apitools.dev/swagger-parser/online/), to parse the [REST/openapiv3.json](https://raw.githubusercontent.com/PagerDuty/api-schema/main/reference/REST/openapiv3.json) spec, we receive the following: ``` This API is valid, but it cannot be shown because it contains circular references...

bug

We use your REST OpenAPI Spec to generate an API client but it seems to be missing attributes in multiple locations. Primariliy the `Integration` schema lacks the `integration_key` attribute. Furthermore...

bug

Incidents triggered by Stackdriver GCP integration (using v1 events API) result in `incident.*` webhook events having a null incident_key. It's unclear if this schema definition needs to be updated, if...

I'm assuming it's in there somewhere, and just not surfaced in the documentation. But I'm trying to pull via the API the slack channel associated with each incident (if one...

For Analytics API - https://api.pagerduty.com/analytics/raw/incidents I cannot find documentation for these attributes and their default values, however these attributes are returned by the API "resolved_by_user_id", "escalation_policy_id", "manual_escalation_count", "escalation_policy_name", "timeout_escalation_count", "resolved_by_user_name"

@palozano __Originally posted by @mail731212 in https://github.com/t3rn/t3rn/pull/1015#discussion_r1222956100__

Hello all, API response on sample **"Create a Ruleset API"** has incorrect JSON key of **"rulesets"** instead of **"ruleset"**. Found this out when I was trying to store the key...