Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 3 Next »

When the connection is configured and the URL endpoint is created, you can use the URL endpoint to transfer attachments from the source cloud instance (where the app is installed) to the target cloud instance.

Make a POST request with the generated URL endpoint. To authenticate your API requests, include an Authorization header in each request. The value of this header should be the API token generated from the API Tokens page. The sample request structure:

 {
  "jql": {JQL_TO_FIND_TARGET_ISSUES}, //REQUIRED
  "sourceKey": {KEY_OF_SOURCE_ISSUE}, //REQUIRED
  "commentId": {ID_OF_COMMENT} //OPTIONAL
}

Parameters:

  • jql (string) - (Required): The JQL query to find target issues.

  • sourceKey (string) - (Required): The key of the source issue.

  • commentId (string) - (Optional): The ID of the comment (if applicable).

Example

POST Request header

curl -H 'Authorization: 46f61f78-e138-4019-85a0-e239878f2c94'

POST Request Body

{
  "jql": "issuekey = ITSM-1",
  "sourceKey": "ITSM-15",
  "commentId": "12345"
}

curl example

curl --request POST \
  --url 'https://api.attach.twinit.com/44221'
  --header 'Accept: application/json' \
  --header 'Authorization: 46f61f78-e138-4019-85a0-e239878f2c94'
  --data ' {
  "jql": "issuekey = ITSM-1",
  "sourceKey": "ITSM-15",
  "commentId": "12345"
}'

  • No labels