{"_id":"5a5fc8285476ef002aa4578f","project":"564e5930c3553e0d003e53d0","version":{"_id":"564e5a9b1560880d008d30dc","project":"564e5930c3553e0d003e53d0","__v":22,"createdAt":"2015-11-19T23:26:19.166Z","releaseDate":"2015-11-19T23:26:19.166Z","categories":["564e5a9b1560880d008d30dd","566318e1f5ca460d00f41896","56631d08cd54d50d005015fa","56631d2a81ad7417006a202c","5668ba19fbd7680d009375f4","5668cb8b10bda80d00797ed9","5668cb9d10bda80d00797eda","56830d8a3f94e00d004e2a7a","56830d9072bb720d0091f594","56830d94cb4d190d0027698e","56830dc44aecbd0d00a464c5","569e90f3c9b43e0d00c4bab1","56a96d338791090d00113bab","56b12d8336d2580d00247877","56c36bf0a869d017002ea55b","56c36bf93d30210d00ea84bb","56c77749b935671700ff0304","56c7ab9e5652c217008e091a","56cb8bdad5c6241d00ef5e61","58aefce02470660f00b54539","58aefd0bebd7370f0078b954","59ca65ca4337830026edf24f"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"Foundation","version_clean":"2.0.0","version":"2"},"category":{"_id":"564e5a9b1560880d008d30dd","pages":["564e5a9c1560880d008d30de","56b217d91bc8490d00701f1b","56c3ccf72d97560d00e23cdc","56c515470fba010d00430759","56c515606889720d0099daf7","56d9e2106fcdd00b0002cc3f"],"project":"564e5930c3553e0d003e53d0","version":"564e5a9b1560880d008d30dc","__v":6,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-11-19T23:20:17.607Z","from_sync":false,"order":0,"slug":"documentation","title":"Basics"},"user":"59e10aa4bf9ac7001a235dd6","githubsync":"","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2018-01-17T22:03:20.139Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":7,"body":"[block:callout]\n{\n  \"type\": \"danger\",\n  \"body\": \"On October 19, 2018 the v1 REST API was fully decommissioned and is no longer operational.\",\n  \"title\": \"V1 REST API Is Now Shut Down\"\n}\n[/block]\nIn July 2016, PagerDuty released our v2 REST API and announced plans to decommission the v1 REST API. This is separate from our Events API which will not be affected. [Learn more about the differences between our APIs here](https://v2.developer.pagerduty.com/docs). \n\n## What happened?\n\nOn April 24, 2018, our v1 REST API entered a decommissioning period. On October 19, 2018 the v1 REST API was fully decommissioned and is no longer operational. \n\nPagerDuty users are no longer able generate new PagerDuty v1 REST API keys. No new PagerDuty features will be available for the v1 REST API. \n\n## Will existing v1 REST API keys continue to work with V2?\n\nOnly if you specify version 2 in the header of your request like so:\n`Accept: application/vnd.pagerduty+json;version=2`\n\nWithout that adjustment, they key will no longer work.\n\n## Will the v1 Events API still be supported?\nThis change only affects the v1 REST API. You can continue to use the v1 Events API as you do today.[Learn more about our the differences between our APIs here](https://v2.developer.pagerduty.com/docs/getting-started).\n\n## I'm using the v1 REST API with a PagerDuty integration. How do I upgrade?\nMost of these integrations have been updated to use the v2 REST API. [Check the \"Steps To Upgrade\" column on this integration list](https://v2.developer.pagerduty.com/v2/docs/v1-rest-api-integrations-update) to see what steps are needed (if any) to upgrade. For those that are not yet upgraded, please use the contact in the last column to check on the status.\n\n[v1 REST API Integrations Update Status Page](https://v2.developer.pagerduty.com/v2/docs/v1-rest-api-integrations-update)\n\n## Why should I upgrade to the new v2 REST API?\n\nThe v2 REST API allows you to take advantage of interactive documentation, simpler API calls, event normalization and consistent naming, new endpoints, and much more. [Learn more about v2 by visiting our FAQs page.](https://v2.developer.pagerduty.com/docs/api-v2-frequently-asked-questions)\n\n## Can I use a v1 API key with the v2 API?\n\nYes, you can continue to use your existing key if you change your code to use v2 API endpoints and modify the Accept header in your code to:  \n`Accept: application/vnd.pagerduty+json;version=2`\n\n[Read our Migration Guide for more information](https://v2.developer.pagerduty.com/docs/migrating-to-api-v2)\n\n## How do I know which of my REST API keys default to v1?\n\nEach REST API key has a default version which is used if you do not specify your version in the request header. [See Versioning](https://v2.developer.pagerduty.com/docs/versioning). \n\n### Account Level API Keys\nAccount owners or admins can see the full list of REST API keys on an account by navigating to **Configuration > API Access** in PagerDuty. The **API Version** column specifies which REST API version the API key uses *by default*. Look for keys with \"v1 Legacy\" in the API Version column.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/e5b9503-api_table.png\",\n        \"api table.png\",\n        1888,\n        318,\n        \"#f6f6f6\"\n      ]\n    }\n  ]\n}\n[/block]\n### User Level API Keys\nYour account may have user level API keys enabled. You can check this by navigating to your User Settings. Click your avatar in the top right corner of your PagerDuty account and select **My Profile**. Once on your profile page, select the **User Settings** tab. If you see an API Access section on this tab, user level API keys are enabled on your account. You should see a similar table where you can check the default version of each key you have created. Each user on your account can manage their user level API tokens on this page.\n\nOnly REST API keys are displayed on the **API Access** page. Events API keys are integration keys and can be found on the **Integrations** tab of each individual service. The Events API will not be impacted by this v1 REST API decommissioning. \n\n## Where can I go for support?\n\nIf you haven’t migrated to v2 yet, we encourage you to get started with the [migration guide](https://v2.developer.pagerduty.com/docs/migrating-to-api-v2) that walks you through the process. Please contact our support team at support:::at:::pagerduty.com if you have questions or encounter problems. \n\n## Special Note To ServiceNow Customers\n\nWhen the v1 REST API is decommissioned on October 19, 2018, version 3.2.1 of the ServiceNow integration will no longer be operational. If you are using this version, you should plan for an upgrade of your ServiceNow integration. [More information can be found here](https://community.pagerduty.com/t/whats-new-pagerduty-v4-integration-for-servicenow/1019).","excerpt":"","slug":"v1-rest-api-decommissioning-faq","type":"basic","title":"v1 REST API Decommissioning FAQ"}

v1 REST API Decommissioning FAQ


[block:callout] { "type": "danger", "body": "On October 19, 2018 the v1 REST API was fully decommissioned and is no longer operational.", "title": "V1 REST API Is Now Shut Down" } [/block] In July 2016, PagerDuty released our v2 REST API and announced plans to decommission the v1 REST API. This is separate from our Events API which will not be affected. [Learn more about the differences between our APIs here](https://v2.developer.pagerduty.com/docs). ## What happened? On April 24, 2018, our v1 REST API entered a decommissioning period. On October 19, 2018 the v1 REST API was fully decommissioned and is no longer operational. PagerDuty users are no longer able generate new PagerDuty v1 REST API keys. No new PagerDuty features will be available for the v1 REST API. ## Will existing v1 REST API keys continue to work with V2? Only if you specify version 2 in the header of your request like so: `Accept: application/vnd.pagerduty+json;version=2` Without that adjustment, they key will no longer work. ## Will the v1 Events API still be supported? This change only affects the v1 REST API. You can continue to use the v1 Events API as you do today.[Learn more about our the differences between our APIs here](https://v2.developer.pagerduty.com/docs/getting-started). ## I'm using the v1 REST API with a PagerDuty integration. How do I upgrade? Most of these integrations have been updated to use the v2 REST API. [Check the "Steps To Upgrade" column on this integration list](https://v2.developer.pagerduty.com/v2/docs/v1-rest-api-integrations-update) to see what steps are needed (if any) to upgrade. For those that are not yet upgraded, please use the contact in the last column to check on the status. [v1 REST API Integrations Update Status Page](https://v2.developer.pagerduty.com/v2/docs/v1-rest-api-integrations-update) ## Why should I upgrade to the new v2 REST API? The v2 REST API allows you to take advantage of interactive documentation, simpler API calls, event normalization and consistent naming, new endpoints, and much more. [Learn more about v2 by visiting our FAQs page.](https://v2.developer.pagerduty.com/docs/api-v2-frequently-asked-questions) ## Can I use a v1 API key with the v2 API? Yes, you can continue to use your existing key if you change your code to use v2 API endpoints and modify the Accept header in your code to: `Accept: application/vnd.pagerduty+json;version=2` [Read our Migration Guide for more information](https://v2.developer.pagerduty.com/docs/migrating-to-api-v2) ## How do I know which of my REST API keys default to v1? Each REST API key has a default version which is used if you do not specify your version in the request header. [See Versioning](https://v2.developer.pagerduty.com/docs/versioning). ### Account Level API Keys Account owners or admins can see the full list of REST API keys on an account by navigating to **Configuration > API Access** in PagerDuty. The **API Version** column specifies which REST API version the API key uses *by default*. Look for keys with "v1 Legacy" in the API Version column. [block:image] { "images": [ { "image": [ "https://files.readme.io/e5b9503-api_table.png", "api table.png", 1888, 318, "#f6f6f6" ] } ] } [/block] ### User Level API Keys Your account may have user level API keys enabled. You can check this by navigating to your User Settings. Click your avatar in the top right corner of your PagerDuty account and select **My Profile**. Once on your profile page, select the **User Settings** tab. If you see an API Access section on this tab, user level API keys are enabled on your account. You should see a similar table where you can check the default version of each key you have created. Each user on your account can manage their user level API tokens on this page. Only REST API keys are displayed on the **API Access** page. Events API keys are integration keys and can be found on the **Integrations** tab of each individual service. The Events API will not be impacted by this v1 REST API decommissioning. ## Where can I go for support? If you haven’t migrated to v2 yet, we encourage you to get started with the [migration guide](https://v2.developer.pagerduty.com/docs/migrating-to-api-v2) that walks you through the process. Please contact our support team at support@pagerduty.com if you have questions or encounter problems. ## Special Note To ServiceNow Customers When the v1 REST API is decommissioned on October 19, 2018, version 3.2.1 of the ServiceNow integration will no longer be operational. If you are using this version, you should plan for an upgrade of your ServiceNow integration. [More information can be found here](https://community.pagerduty.com/t/whats-new-pagerduty-v4-integration-for-servicenow/1019).