Use of APIs to External Products & Licensing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2018 04:22 AM
What is the license model when using APIs to communicate to external third party products?
Thanks,
Alex
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2018 04:33 AM
Hi Alex,
There is no licensing fee required for viewing the queue/transactions within an API, however if in case you are granting update access to any of the users on a ticket which has been created via API, then it shall be treated as a fulfiller license as the user is updating the ticket through UI/front end.
Similarly, the service account used for Integration has usually got "soap", "REST", or a "web_service_admin" role. This is considered to be a platform run time license on ServiceNow.
Regards,
Mishu
Note: Please mark this response as "Helpful", if in case it has resolved your query.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2018 04:51 AM
Thank you for the response. To further elaborate if we make an API call to Slack from ServiceNow to communicate incident information would there be a license fee? If Slack makes an API call to ServiceNow to update an incident would there be a license fee?
Thanks,
Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2018 05:11 AM
Hi Alex,
If in case a Service account has been created for Integration between ServiceNow and Slack via REST for Inbound and via SOAP for Outbound, then in both the cases "rest" and "soap" roles shall be granted to the service account, in order to perform a hand shake/authentication between the two platforms. A "rest" and a "soap" role involves a platform run time license fee.
Regards,
Mishu
Note: Please mark this response as "Helpful", if in case it has resolved your query.
