Problem Definition

Currently , for Application Link , user only can send GET and DELETE request . But , POST is not available to create application link.

Suggested Solution

Provide POST function for creating Application Link

Workaround

As a workaround, you can use the unofficial endpoint discussed in the following thread in the Atlassian Community (it works for both, Server and Cloud): Jira cloud addon: use API to create oauth1 application link

• Endpoint: 

  https://xxxxxxx.atlassian.net/rest/applinks/1.0/applicationlinkForm/createAppLink
  

• Request Body: 

  {
  "applicationLink": {
  "typeId": "generic",
  "name": "myapp",
  "displayUrl": "http://example.com",
  "rpcUrl": "http://example.com",
  "isPrimary": false,
  "isSystem": true
  },
  "username": "admin",
  "password": "admin",
  "customRpcURL": false,
  "rpcUrl": "",
  "createTwoWayLink": false,
  "configFormValues": {
  "trustEachOther": false,
  "shareUserbase": false
  }
  }
  

   

• Response Body:

  <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  <createdApplicationLink>
  <applicationLink>
  <link href="https://xxxxxxx.atlassian.net/rest/applinks/latest/applicationlink/a9b9f043-36ce-3181-a08e-774e01113b31" rel="self"/>
  <id>a9b9f043-36ce-3181-a08e-774e01113b31</id>
  <typeId>generic</typeId>
  <name>myapp</name>
  <displayUrl>http://example.com</displayUrl>
  <iconUrl>https://xxxxxxx.atlassian.net/s/-w84psc/b/11/14089203f537b6cb29f73c5809f577b4a6a0c922/_/download/resources/com.atlassian.applinks.applinks-plugin:applinks-images/images/types/16generic.png</iconUrl>
  <iconUri>https://xxxxxxx.atlassian.net/s/-w84psc/b/11/14089203f537b6cb29f73c5809f577b4a6a0c922/_/download/resources/com.atlassian.applinks.applinks-plugin:applinks-images/images/config/logos/128x128/128generic.png</iconUri>
  <rpcUrl>http://example.com</rpcUrl>
  <isPrimary>false</isPrimary>
  <isSystem>false</isSystem>
  </applicationLink>
  <autoConfigurationSuccessful>true</autoConfigurationSuccessful>
  </createdApplicationLink>
  

   

Please notice that this is just a workaround: the endpoint is not officially documented and it may change without prior notice. Please review the thread for further details.