---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Send inbound events using token

# Creation of webhooks to send inbound events to DevOps Change Velocity using token {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
You must create webhooks to send inbound events to DevOps Change Velocity using token based authentication.
To send inbound events to a ServiceNow instance, you must use the following API endpoint structure:

    <instance_url>/api/sn_devops/v2/devops/tool/{capability}?toolId=<toolId>

where capability can be plan, code, or orchestration.

You can copy the details like the tool Id, instance URL, and so on by selecting Configure manually from the tool record or in the configure step while onboarding the tool. You can then select
Copy in the appropriate field to copy the value to your clipboard. The field label changes to Copied, but you can copy multiple times. The following image displays the page
from where the values can be copied for the GitHub tool in DevOps Change Velocity.  
For token authentication, you must pass the token as part of the authorization header or query parameters as the endpoints are secured. You can use one of the following methods:

* Pass the token as a header by using the following format: <kbd class="ph userinput">Header Name: Authorization Header Value: sn_devops.DevOpsToken &lt;ToolId&gt;:&lt;Token&gt;</kbd>, where \<ToolId\> is the ID of the tool, and \<Token\> is the authentication token copied from the Tool Record page.
* Pass the token as a query parameter in the URL: <kbd class="ph userinput">&lt;instance_url&gt;/api/sn_devops/v2/devops/tool/{capability}?toolId=&lt;toolId&gt;&amp;ni.nolog.token=&lt;Token&gt;</kbd>, where \<ToolId\> is the ID of the tool, and \<Token\> is the authentication token copied from the Tool Record page.

For Basic authentication, you can use the following V1 endpoint: <kbd class="ph userinput">https://user:password@&lt;instance_url&gt;/api/sn_devops/v1/devops/tool/{capability}?toolId=&lt;toolId&gt;</kbd>, replace user and password with your
ServiceNow credentials.

If you have a custom tool or a different authentication method, you can implement your own authentication logic. For example, you can implement an authenticateToken function in your handler class. The function should verify
the token and ensure proper authentication. You must have the admin role in ServiceNow to implement your own authentication logic.