• Created by Unknown User (aleksandra.luszowska@infodesign.pl), last updated on Feb 08, 2018 2 minute read

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Custom SMS allows to configure the SMS provider of your choice. You will have to manually configure and make changes to your SMS provider settings such as, e.g. authorization type (token or basic), your provider's URL address and JSON data. 

Custom SMS Provider enables you to send REST calls. 

Adding a Custom text message provider:

  1. Log in as a user with the Jira Administrators global permission.
  2. Choose the cog icon> Add-ons. Select SLA PowerBox > Notification Providers to open the SLA Notification Providers page.
    Tip: Keyboard shortcut: g + g + start typing notification providers...
  3. Click the Add Provider button.  
  4. Select SMS / REST API Gateway
  5. Click the Next button.
  6. Select the Custom text message provider. 
  7. Confirm with the Next button. 
  8. Fill in all required fields which are listed and described below.
  9. Save the changes with the Create button. 







Configuration fields:


Provider Name - it is a Notification Provider display name and allows you to identify your notification.

Description - a short description of your notification.

Header Content type - the type of data that the SMS provider expects to receive. 

URL - enter your provider URL address.

Authorization type - select from two authorization types: basic and token. 

  • Basic authorization  is based on your username and password,
  • Token authorization requires a unique token from the message provider.

Username - enter your username.

Password - enter your password.

Token - it is a token required for authorization by your provider. 

User phone key -  is the name that uniquely identifies the user's phone number and has to be specified in: User Management > Edit User Properties > Add User Property.

Params - add required parameters to the provider: key and value. 

Json request data - here you can put predefined tags to the input value.

Error interpretation - how the server response should classify attempts as errors, select from two interpretation types:

  • Status code - when it is based on the status code,
  • Response text - where you can put an error text (case sensitive). This text will be interpreted as an error if the response includes this text.


  • No labels