Hello together,
I received the following swagger file Swagger Exalate
Unfortunately, there is no description how to authenticate to use this API and the endpoints itself has also nearly no description. How can I authenticate and which endpoint should I use to start the synchronization process?
Thanks and regards
What system are you using please i.e. what system would you like to start the sync on? Is it Jira Cloud? And I am guessing you want to do this externally i.e. make a call to a REST endpoint and have that trigger the sync? It would also be nice to understand the big picture of what you are trying to achieve here please. For instance, if it is simply about starting the sync, I would recommend making a call to the actual Jira API to add a label (as an example). This can be set as a trigger condition for Exalate to then automatically pick it up - not sure if it is relevant, but do let me know please.
Thanks
Majid
Hi,
Yes, I am using Jira Cloud to Azure DevOps connection.
The big picture is quite complex:
Unfortunately, Exalate has limited functionality and we need the possibility that only specific user groups can trigger the synchronization process between the two systems. In Exalate I can only distinguish between Admin and All users what is not sufficient for us.
In case of having an API endpoint that can be called to start the synchronization process, I can create a Jira Automation Rule which uses that endpoint. And the execution of the Jira Autiomation Rule can be limited to specific user groups.
Was that understandable for you?
Jens
Thank you for expanding on the use case. I would still have done it via the Exalate scripts i.e. checked the user (assignee/ reporter) attributes to verify if this is the user that is allowed to sync or not, and then drop the transaction in the Outgoing script based on this. However, I will try to provide you an endpoint and auth info to be able to use it in the external script as well.
Thanks
Would be really great if you can provide me an endpoint and information about authentication!
I guess these endpoints are worthful for other customers, too. Maybe you should think about providing an “official” REST API that can be used 
Hi @JeHe ,
Apologies for the relatively long response time here! But I took time to dive deeper into the problem and explore what the possibilities were. Here is a short summary:
As of now, it is very possible to call a REST end point in order to utilize the Exalate API. For instance, you require to call an endpoint to Exalate a ticket. In order to do that,
Endpoint: https://jcloudnode-vzwc-fwga-gizn-hhga.exalate.cloud/rest/issuehub/4.0/entity/cm-2678/connection/1409/exalate
Here, vzwc-fwga-gizn-hhga is the node id.
CM-2678 is the issue key that is to be exalated.
1409 is the connection_id.
In order to authenticate, you need to add a x-exalate-jwt header, with the value of a valid JWT token. The session JWT can be gotten from a working UI but it will expire in short time:
Please note that this API was not meant for clients and hence, lacks a more robust authentication mechanism that would allow you to use it externally. We have put an internal request in with engineering in order for this to be available for clients.
Apologies for the inconvenience.
Thanks
Majid
Hi Majid,
thanks for providing the endpoint. Unfortunately, the solution with the UI to retrieve the access token is not feasible. I need an API call that returns me the JWT.
Thanks and regards
Fully agreed, and this is why I was even reluctant to share it - as it doesnt really help you.
I have requested our product team to prioritize this. You can also help by providing feedback on our Product Portal if you want.
Thanks
Majid
