Hi David,
Let me see if I can help address your questions. So per the documentation, I created an API Trigger first:
Next, in regards to authentication, the recommendation is to set up a PAT Token. End result should look something like the following (I highlighted the minimal job scopes I gave my PAT token):
You then want to input said token into your 3rd party application as well as your slug url. In my case, I used Postman:
Copy Slug URL from API Trigger
Enter Values in Postman
Once I clicked “Send” in Postman, then the job instantly spun up on the Orchestrator side:
In short, API triggers are tied to the api call generated/the slug url you specify when creating the trigger and not IS connections specifically. Please let me know if this helps!