This api token should be treated as any other credential as anyone with it can submit data to an event source.
Koppla - Project Configuration Screen - Accessible by Project Admins Only
How to send the data
Each connection data needs to provide 5 items:
This is the title of the remote data and will appear bolded in the Jira issue
The description of the remote data piece.
A text string of date (example 2020/12/31). If none is provided - the current date is assumed.
The value that this refers to in the field that the project administrator configured.
Once you have the information above, you can trigger a HTTP POST to the trigger url.
The authorization header should contain the API Token and the body of the request should be a JSON formatted string including the title, description, time and url.
At the end of the trigger url append &key=[event source key]&value=[the lookup value] (replace [the lookup value] with the value and [event source key] with the even source key).
curl -X POST \
-H "authorization:hwdhfjshdfjhsd3SDFFasdd" \
"title":"This happened a while back",
"description":"This is the description of the request"
This will trigger ingest an item from Feb 3, 2019 with a title of “This happened a while back” and will be shown on an issue in the project where the field has a value of BBB.
How to remove data
Any data sent in has to be removed by the project administrator through the user interface.
Data limitation information
Each lookup value can have multiple values sent in however the total size of all of the data stored for a single look up value is limited to 32k. Once you exceed this, the earliest values are removed in order to make room for the new entry.