{"_id":"5769f0522e9853220083281f","__v":2,"githubsync":"","project":"564e5930c3553e0d003e53d0","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"},"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"},"user":"564e5788230d7c1700c9073e","parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-06-22T01:56:34.822Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":6,"body":"##What are the changes in REST API v2? \n\nThe v2 REST API will enable developers and non-developers to extend the PagerDuty platform with ease. Additionally, customers will have access to far more comprehensive documentation including reliable client libraries/SDKs, so they can deliver with more agility and performance when building new PagerDuty tools against the PagerDuty API.\n\n##What are the benefits of the newer REST API? Why should I switch?\n\nREST API v2 features include the following:\n\n  * Our documentation now allows you to try the API inside your browser\n  * The API calls no longer need redundant information like your subdomain or requester_id\n  * Consistent naming and access of fields and parameterization\n  * Improvements to multiple endpoints for greater speed and performance \n  * New API endpoints\n  * An “Account Abilities” API that allows our mobile app to feature gate abilities by account\n  * Create or leverage out of the box [add-ons](https://v2.developer.pagerduty.com/page/api-reference#!/Add-ons/get_addons) to extend functionality for your users within the PagerDuty experience\n  * An [on-calls endpoint](https://v2.developer.pagerduty.com/v2/page/api-reference#!/On-Calls/get_oncalls) that makes it easy to get information about who is on call for what and when\n\nThe benefits of migrating over to the v2 REST API include improved consistency and ease of development, more endpoints and potential add-ons (both pre-built and custom/edge cases), as well as new and improved supporting documentation, best practices and SDKs. \n\nWe strongly encourage you to migrate to v2, as all new features moving forward will only be available on v2, and will not be available on the previous version.\n\n##What support can I expect from PagerDuty in making the switch?\n\nCustomers can expect full support for requests related to this migration — please direct all inquiries to [support:::at:::pagerduty.com](mailto:support@pagerduty.com). We have created a detailed [migration guide](doc:migrating-to-api-v2) to take you through the step-by-step process for migration, and our client libraries/SDKs include code samples to help streamline that process. \n\nOur support team has [updated documentation](https://support.pagerduty.com/hc/en-us/articles/214794907-What-is-the-difference-between-PagerDuty-APIs-) and is ready to assist with any questions or issues associated with the migration. You can also find [resources for leveraging third party tools for v2](https://support.pagerduty.com/hc/en-us/sections/200550700-Third-Party-Tools).\n\nWe look forward to partnering with you to help you with your migration.\n\n##When does the support for the previous API version end?\n\nThe v1 REST API is entering a decommissioning period on April 24. [Read our FAQ on the decommissioning here](https://v2.developer.pagerduty.com/v2/docs/v1-rest-api-decommissioning-faq).\n\nAs of July 6, 2016, no new features will be released for v1. \n\n\n##What will happen to integrations?\n\nMost integrations, which use the *[Events API (v1)](/docs/trigger-events)* as distinct from the [REST API (v1)](https://v1.developer.pagerduty.com), will not be affected. Support will end only for the v1 REST API, and not for the Events API.\n\n##Who is eligible for API v2?\n\nThe Enterprise, Standard and Basic plans support API v2, for no additional charge.\n\n##Who do I contact for more information? \n\nPlease contact our support team at [support@pagerduty.com](mailto:support@pagerduty.com) if you have any questions.","excerpt":"","slug":"api-v2-frequently-asked-questions","type":"basic","title":"API v2 FAQ"}
##What are the changes in REST API v2? The v2 REST API will enable developers and non-developers to extend the PagerDuty platform with ease. Additionally, customers will have access to far more comprehensive documentation including reliable client libraries/SDKs, so they can deliver with more agility and performance when building new PagerDuty tools against the PagerDuty API. ##What are the benefits of the newer REST API? Why should I switch? REST API v2 features include the following: * Our documentation now allows you to try the API inside your browser * The API calls no longer need redundant information like your subdomain or requester_id * Consistent naming and access of fields and parameterization * Improvements to multiple endpoints for greater speed and performance * New API endpoints * An “Account Abilities” API that allows our mobile app to feature gate abilities by account * Create or leverage out of the box [add-ons](https://v2.developer.pagerduty.com/page/api-reference#!/Add-ons/get_addons) to extend functionality for your users within the PagerDuty experience * An [on-calls endpoint](https://v2.developer.pagerduty.com/v2/page/api-reference#!/On-Calls/get_oncalls) that makes it easy to get information about who is on call for what and when The benefits of migrating over to the v2 REST API include improved consistency and ease of development, more endpoints and potential add-ons (both pre-built and custom/edge cases), as well as new and improved supporting documentation, best practices and SDKs. We strongly encourage you to migrate to v2, as all new features moving forward will only be available on v2, and will not be available on the previous version. ##What support can I expect from PagerDuty in making the switch? Customers can expect full support for requests related to this migration — please direct all inquiries to [support@pagerduty.com](mailto:support@pagerduty.com). We have created a detailed [migration guide](doc:migrating-to-api-v2) to take you through the step-by-step process for migration, and our client libraries/SDKs include code samples to help streamline that process. Our support team has [updated documentation](https://support.pagerduty.com/hc/en-us/articles/214794907-What-is-the-difference-between-PagerDuty-APIs-) and is ready to assist with any questions or issues associated with the migration. You can also find [resources for leveraging third party tools for v2](https://support.pagerduty.com/hc/en-us/sections/200550700-Third-Party-Tools). We look forward to partnering with you to help you with your migration. ##When does the support for the previous API version end? The v1 REST API is entering a decommissioning period on April 24. [Read our FAQ on the decommissioning here](https://v2.developer.pagerduty.com/v2/docs/v1-rest-api-decommissioning-faq). As of July 6, 2016, no new features will be released for v1. ##What will happen to integrations? Most integrations, which use the *[Events API (v1)](/docs/trigger-events)* as distinct from the [REST API (v1)](https://v1.developer.pagerduty.com), will not be affected. Support will end only for the v1 REST API, and not for the Events API. ##Who is eligible for API v2? The Enterprise, Standard and Basic plans support API v2, for no additional charge. ##Who do I contact for more information? Please contact our support team at [support@pagerduty.com](mailto:support@pagerduty.com) if you have any questions.