Replaced all support emails with developer support on the dev portal. (iZettle#162)

Author: Astro-Choco

README.md

@@ -52,16 +52,4 @@ When you have a developer account, choose one of the following app types based o
 * To build a partner-hosted app that is hosted by you as an integrator, [create a partner-hosted app](oauth-api/user-guides/create-an-app/create-a-partner-hosted-app.md).
 
 ## Get help
-Contact our [Integrations team](mailto:[email protected]) for more information. 
-
-When contacting the Integrations team, please provide the following information:
-
-* Description about the issue. That includes:
-    * What's the integration used for?
-    * Which API or APIs are you using?
-    * What went wrong? 
-
-* Information about affected merchants. That includes:
-    * Emails of affected merchants.
-    * UUIDs and organisation UUIDs of the affected merchants.
-      To fetch UUIDs and organisation UUIDs, use the `GET users/self` endpoint of the OAuth API. For more information about using the endpoint, see [Get user info](authorization.md/#get-user-info).
+Contact our developer support at [Zettle Developer Portal](https://developer.zettle.com).

finance-api/finance-api-migration-guide.md

@@ -42,5 +42,4 @@ These changes apply to both input parameter `includeTransactionType` and `origin
 and also apply to historical data.
 
 ## Support
-If you have any questions, please contact our service desk by sending an email to our 
-[Integrations team](mailto:[email protected]).
+If you have any questions, please contact our developer support at [Zettle Developer Portal](https://developer.zettle.com).

incidents.md

@@ -1,6 +1,6 @@
 Incidents
 =====================
-If you have questions about any incident, contact our [Integrations team](mailto:api@zettle.com).
+If you have questions about any incident, contact our developer support at [Zettle Developer Portal](https://developer.zettle.com).
 
 ## March 2021
 ### Finance API returned wrong transaction type for transactions made with cards.

oauth-api/zettle-password-grant-migration-guide/zettle-password-grant-migration-guide.md

@@ -13,7 +13,7 @@ The Password grant for Zettle integrations is now deprecated and will be removed
 Update the integration to use an authentication grant supported by Zettle. You can find more information in this document and in the [Zettle OAuth2 API documentation](../../authorization.md).
 
 ## Support 
-If you have any questions, please contact our service desk by sending an email to our [Integrations team](mailto:api@zettle.com). 
+If you have any questions, please contact our developer support at [Zettle Developer Portal](https://developer.zettle.com). 
 
 ## Technical details
 Zettle API uses the OAuth 2.0 Authorization Framework. The Assertion grant is recommend to keep your integration secure. For more information about the assertion grant and other authentication flows, read more in the [Zettle OAuth2 API documentation](../../authorization.md). 

pusher-api/api-reference.md

@@ -90,7 +90,7 @@ See example [Create a webhook subscription](#create-a-webhook-subscription).
 |403 Forbidden | Returned when the scope being used in the request is incorrect. <br/> E.g. If you provide a permission scope of `READ:PRODUCT` while creating a subscription for `PurchaseCreated` then the Pusher API will return 403 in the response.
 |400 Bad Request |Returned when one of the following occurs: <br/><ul><li>The `transportName` or `uuid` is missing in the request.</li><li>A subscription with the `uuid` passed in request already exists.</li><li>The `destination` is not accessible.</li></ul>
 |422 Unprocessable Entity |Returned when one of the following occurs: <br/><ul><li>The `destination` or `contactEmail` is missing in the request.</li><li>The `contactEmail` has an invalid value for email address.</li></ul>
-|500 Internal Server Error|Returned when one of the following occurs: <br/><ul><li>The `destination` responded with a non-successful HTTP response code.</li><li>The Pusher API encountered an internal server error. In case this error persists, contact [support](mailto:api@zettle.com).</li></ul>
+|500 Internal Server Error|Returned when one of the following occurs: <br/><ul><li>The `destination` responded with a non-successful HTTP response code.</li><li>The Pusher API encountered an internal server error. In case this error persists, contact our developer support at [Zettle Developer Portal](https://developer.zettle.com).</li></ul>
 </details>
 
 <details open="true">
@@ -139,7 +139,7 @@ See example [Get webhook subscriptions](#get-webhook-subscriptions).
 |---- |----
 |200 OK| Returned when the Pusher API returns a collection of subscriptions for the client. 
 |401 Unauthorized |Returned when one of the following occurs: <br/><ul><li>The authentication information is missing in the request.</li><li>The authentication token has expired.</li><li>The authentication token is invalid.</li></ul> 
-|500 Internal Server Error| Returned when the Pusher API encounters an internal server error. In case this error persists, contact [support](mailto:api@zettle.com).
+|500 Internal Server Error| Returned when the Pusher API encounters an internal server error. In case this error persists, contact our developer support at [Zettle Developer Portal](https://developer.zettle.com).
 </details>
 
 
@@ -199,7 +199,7 @@ See example [Update a webhook subscription](#update-a-webhook-subscription).
 |405 Method Not Allowed | Returned when the `subscriptionUuid` is missing in the request.
 |400 Bad Request| Returned when the `eventNames` parameter contains events that are not supported by the Pusher API.
 |422 Unprocessable Entity| Returned when one of the following occurs: <br/><ul><li> Returned if the `destination` specified in the request is empty.</li><li>The `destination` value is not a valid HTTPS URL.</li></ul>
-|500 Internal Server Error| Returned when the Pusher API encounters an internal server error. In case this error persists, contact [support](mailto:api@zettle.com).
+|500 Internal Server Error| Returned when the Pusher API encounters an internal server error. In case this error persists, contact our developer support at [Zettle Developer Portal](https://developer.zettle.com).
 </details>
 
 <details open="true">
@@ -239,7 +239,7 @@ See example [Delete a webhook subscription](#delete-a-webhook-subscription).
 |204 No Content| Returned when the Pusher API deletes the subscription successfully.
 |401 Unauthorized |Returned when one of the following occurs: <br/><ul><li>The authentication information is missing in the request.</li><li>The authentication token has expired.</li><li>The authentication token is invalid.</li></ul>
 |404 Not Found|Returned when one of the following occurs: <br/><ul><li>The `subscriptionUuid` is missing in the request.</li><li>A subscription was not found for the `subscriptionUuid` passed in the request</li></ul> 
-|500 Internal Server Error| Returned when the Pusher API encounters an internal server error. In case this error persists, contact [support](mailto:api@zettle.com).
+|500 Internal Server Error| Returned when the Pusher API encounters an internal server error. In case this error persists, contact our developer support at [Zettle Developer Portal](https://developer.zettle.com).
 </details>
 
 <details open="true">

pusher-api/troubleshooting.md

@@ -78,9 +78,7 @@ This error usually returns when the destination URL is not up and running. Check
     
 3. If you receive the error in a production environment, make sure that the destination URL is up and running.
 
-4. Is HTTP status code 2xx returned?
-    * Yes: The error is fixed.
-    * No: Contact [Integrations team](mailto:[email protected]). 
+4. If you get the HTTP status code 2xx, then the error is fixed.
 
 ## Related API reference
 * [Pusher API reference](api-reference.md)