Labelling Incidents through Integrations

[TejpalB]

I have recently done the ServiceNow Integration to create the ServiceNow Incidents. I am using service now REST APIs to create the incidents. After creating the incidents through integrations, I want to sync the incidents in my system. For that, I need to query the service now incidents, but as a result, I only want the incidents that are created by the Integration which I have created. 

I tried to put the integration source details in the label,  It works, but I found that we can add a label to an incident using the below label entry API.

https://{{instance}}.service-now.com/api/now/table/label_entry

But, it requires the below scopes. Which are only available for maint role and not available for System Admin by default

label_entry.table 
label_entry_table_key
label_entry

 So, my question is the labeling can only be done through UI and not through the REST APIs? 

Is this feature only available for SNOW maint role?

What is the standard practice for labeling the service now incidents through external integrations using REST APIs?

Or, to solve my problem where I want to query the incidents which created by my integration, Is there any other solution?

[Nia McCash]

I can't answer your questions about the API but if there is some other way, in the platform, of distinguishing the incidents created through the API - that is there is some query/filter you can run in the platform to know what was created via the integration, then I would look into automatic tagging: https://docs.servicenow.com/bundle/utah-platform-user-interface/page/use/common-ui-elements/concept/...

[Mike_R]

What's the use case for the label?

If you're just trying to add additional information such as the integration source, you can write to these fields instead

Correlation ID, and Correlation display.

[TejpalB]

Thanks @Mike_R for responding.

My use case is, I want to query the incidents which are created by my integration using APIs. I dont want to include the results other than the incidents created through UI or any other person or any other integration.

So, I wanted to put some details/context in the incident so that I can filter the incident based on it.

So, I tried with a label. but it has some limitations.

I found correlation id is being used for a different purpose. like storing the unique id of the ticket on a local third party instance

[MPD Odijk]

In an ideal world each integration gets a unique sys_user record that is used to access the system. If that is the case with you, using the value of the sys_created_by could be all you need...