How to generate an Application Links Configuration Summary

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

When diagnosing Application Link issues, support may ask to provide details on the configuration of your application link. Below are a few methods on how to provide this information.

Solution

Command Line Solution

  • From your workstation, fetch a list of all the application links configured in Application A

  • Open up a terminal and run the following command

    curl -u ADMIN_USERNAME:ADMIN_PASSWORD -i -H "Accept: application/json" -X GET APPLICATION_A_BASE_URL/rest/applinks/latest/applicationlink
  • Note the value of "id" for the link to Application B.

  • Fetch the configuration details for the link to Application B, inserting the correct applink ID from the prior query:

    curl -u ADMIN_USERNAME:ADMIN_PASSWORD -i -H "Accept: application/json" -X GET APPLICATION_A_BASE_URL/rest/applinks/latest/applicationlink/APPLICATION_B_APPLINK_ID curl -u ADMIN_USERNAME:ADMIN_PASSWORD -i -H "Accept: application/json" -X GET APPLICATION_A_BASE_URL/rest/applinks/latest/applicationlink/APPLICATION_B_APPLINK_ID/authentication

    ℹ️ If the authentication query returns a 404, please attempt the query below as well. This is due to a recent change in our rest API

    curl -u ADMIN_USERNAME:ADMIN_PASSWORD -i -H "Accept: application/json" -X GET APPLICATION_A_BASE_URL/rest/applinks/latest/applicationlink/APPLICATION_B_APPLINK_ID/authentication/provider
  • Repeat the instructions above for Application B, replacing the BASE_URL, ADMIN_USERNAME, and ADMIN_PASSWORD as appropriate.

    ℹ️ Please note that if you are using BasicAuth (not recommended) then the configured username and password will be returned in the JSON data for /authentication. Please remove the password prior to sharing this data with us.

Browser Solution

  • Install the Postman - REST Client

  • Load the plugin and GET the URL:

    APPLICATION_A_BASE_URL/rest/applinks/latest/applicationlink
  • Ensure the Content Type is set to JSON, otherwise errors will occur. The screenshot below illustrates the configuration.

    (Auto-migrated image: description temporarily unavailable)
  • Take the APPLINK_ID of the application link in question and run the following two commands in Postman

    APPLICATION_A_BASE_URL/rest/applinks/latest/applicationlink/APPLICATION_B_APPLINK_ID APPLICATION_A_BASE_URL/rest/applinks/latest/applicationlink/APPLICATION_B_APPLINK_ID/authentication

    ℹ️ If the authentication query returns a 404, please attempt the query below as well. This is due to a recent change in our rest API

    curl -u ADMIN_USERNAME:ADMIN_PASSWORD -i -H "Accept: application/json" -X GET APPLICATION_A_BASE_URL/rest/applinks/latest/applicationlink/APPLICATION_B_APPLINK_ID/authentication/provider
  • Repeat the instructions above for Application B, replacing the BASE_URL, ADMIN_USERNAME, and ADMIN_PASSWORD as appropriate.

Alternative Solution

If neither solution work, the alternative is to provide screenshots of your application link configuration. In which case, navigate to the Application Link Page on Application A and then edit Application B to provide screenshots of the following tabs

  • Application Details

  • Outgoing Authentication > Trusted Applications

  • Outgoing Authentication > OAuth

  • Outgoing Authentication > Basic Access

  • Incoming Authentication > Trusted Applications

  • Incoming Authentication > OAuth

  • Incoming Authentication > Basic Access

Updated on May 22, 2025

Still need help?

The Atlassian Community is here for you.