--- title: TISC Intel Exchange API description: Enables external systems to share threat intelligence data with the Threat Intelligence Security Center \(TISC\) application.Shares threat intelligence data from an external source with the Threat Intelligence Security Center \(TISC\) application. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/api-reference/rest-apis/tisc-intel-ex-api.html release: australia product: REST APIs classification: rest-apis topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 7 breadcrumb: [REST API reference, API reference, API implementation and reference] --- # TISC Intel Exchange API Enables external systems to share threat intelligence data with the Threat Intelligence Security Center \(TISC\) application. This API requires the Threat Intelligence Security Center application, which is available on the ServiceNow Store. For additional information about TISC, see [Threat Intelligence Security Center](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/security-management/tisc-landing-page.md). This API runs in the `sn_sec_tisc` namespace. The calling user must have the sn\_sec\_tisc.api\_post\_intel role. The current version of this API is `v1`. **Parent Topic:**[REST API reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/rest-apis/api-rest.md) ## TISC Intel Exchange - POST /sn\_sec\_tisc/tisc\_intel\_sharing\_api/post\_intel Shares threat intelligence data from an external source with the Threat Intelligence Security Center \(TISC\) application. This endpoint creates an inbound intelligence record, as well as records for indicators, objects, and observables. Indicator records are created in the Indicator Source \[sn\_sec\_tisc\_indicator\_source\] table. Object records are created in the following tables that extend Object Source \[sn\_sec\_tisc\_object\_source\]. - Attack Pattern Source \[sn\_sec\_tisc\_attack\_pattern\_source\] - Campaign Source \[sn\_sec\_tisc\_campaign\_source\] - Course of Action Source \[sn\_sec\_tisc\_course\_of\_action\_source\] - Data Component \[sn\_sec\_tisc\_data\_component\] - Data Source \[sn\_sec\_tisc\_data\_source\] - Identity Source \[sn\_sec\_tisc\_identity\_source\] - Infrastructure Source \[sn\_sec\_tisc\_infrastructure\_source\] - Intrusion Set Source \[sn\_sec\_tisc\_intrusion\_set\_source\] - Location Source \[sn\_sec\_tisc\_location\_source\] - Malware Analysis Source \[sn\_sec\_tisc\_malware\_analysis\_source\] - Malware Source \[sn\_sec\_tisc\_malware\_source\] - Marking Definition Source \[sn\_sec\_tisc\_marking\_definition\_source\] - Object Sighting Source \[sn\_sec\_tisc\_object\_sighting\_source\] - Observed Data Source \[sn\_sec\_tisc\_observed\_data\_source\] - Threat Actor Source \[sn\_sec\_tisc\_threat\_actor\_source\] - Threat Event Source \[sn\_sec\_tisc\_threat\_event\_source\] - Threat Grouping Source \[sn\_sec\_tisc\_threat\_grouping\_source\] - Threat Note Source \[sn\_sec\_tisc\_threat\_note\_source\] - Threat Opinion Source \[sn\_sec\_tisc\_threat\_opinion\_source\] - Threat Report Source \[sn\_sec\_tisc\_threat\_report\_source\] - Tool Source \[sn\_sec\_tisc\_tool\_source\] - Vulnerability Source \[sn\_sec\_tisc\_vulnerability\_source\] Observable records are created in the following tables that extend Observable Source \[sn\_sec\_tisc\_observable\_source\]. - Artifact Source \[sn\_sec\_tisc\_artifact\_source\] - AS Number Source \[sn\_sec\_tisc\_as\_number\_source\] - Directory Source \[sn\_sec\_tisc\_directory\_source\] - Domain Name Source \[sn\_sec\_tisc\_domain\_name\_source\] - Email Address Source \[sn\_sec\_tisc\_email\_address\_source\] - Email Message Source \[sn\_sec\_tisc\_email\_message\_source\] - Email Subject Source \[sn\_sec\_tisc\_email\_subject\_source\] - File Source \[sn\_sec\_tisc\_file\_source\] - IPv4 Address Source \[sn\_sec\_tisc\_ipv4\_address\_source\] - IPv4 CIDR Source \[sn\_sec\_tisc\_ipv4\_cidr\_source\] - IPv6 Address Source \[sn\_sec\_tisc\_ipv6\_address\_source\] - IPv6 CIDR Source \[sn\_sec\_tisc\_ipv6\_cidr\_source\] - MAC Address Source \[sn\_sec\_tisc\_mac\_address\_source\] - MD5 Hash Source \[sn\_sec\_tisc\_md5\_hash\_source\] - Mutex Name Source \[sn\_sec\_tisc\_mutex\_name\_source\] - Network Source \[sn\_sec\_tisc\_network\_source\] - Other Observable Source \[sn\_sec\_tisc\_other\_observable\_source\] - Process Source \[sn\_sec\_tisc\_process\_source\] - SHA1 Hash Source \[sn\_sec\_tisc\_sha1\_hash\_source\] - SHA256 Hash Source \[sn\_sec\_tisc\_sha256\_hash\_source\] - SHA512 Hash Source \[sn\_sec\_tisc\_sha512\_hash\_source\] - Software Source \[sn\_sec\_tisc\_software\_source\] - URL Source \[sn\_sec\_tisc\_url\_source\] - User Account Source \[sn\_sec\_tisc\_user\_account\_source\] - Windows Registry Key Source \[sn\_sec\_tisc\_windows\_registry\_key\_source\] - X.509 Certificate Source \[sn\_sec\_tisc\_x\_509\_certificate\_source\] ### URL format Versioned URL: `/api/sn_sec_tisc/{api_version}/tisc_intel_sharing_api/post_intel` Default URL: `/api/sn_sec_tisc/tisc_intel_sharing_api/post_intel` ### Supported request parameters
| Name | Description |
|---|---|
| api\_version | Optional. Version of the endpoint to access. For example, `v1` or `v2`. Only specify this value to use an endpoint version other than the latest. Data type: String |
| Header | Description |
|---|---|
| Accept | Data format of the response body. Only supports **application/json**. |
| Profile-GUID | Unique identifier of the inbound intelligence profile configured in the receiving instance that data is being shared with.To obtain the unique identifier, navigate to the **Administration** tab of **Threat Intelligence Security Center**, then go to **Inbound Intelligence Profiles** and click the profile you want to use. On the profile page, select **Copy Profile ID** or **Email Profile Details**. |
| Shared-Intel-Format | Format of the data being shared.Possible values: - STIX 2.1 - MISP |
| Status code | Description |
|---|---|
| 200 | Successful. The request was successfully processed. |
| 400 | Bad Request. Possible errors: - Missing `Shared-Intel-Format` in request header. - Missing `Profile-GUID` in request header. - `Shared-Intel-Format` header contains unsupported values. - `Profile-GUID` header refers to a profile that isn't enabled or doesn't exist. - Profile doesn't support intelligence sharing in the format specified by the `Shared-Intel-Format` header. - Authenticated user doesn't have permission to submit intelligence to the specified profile. |
| 422 | Unprocessable Content. The request body doesn't follow the format specified by the `Shared-Intel-Format` request header. |
| 500 | Internal server error. An unexpected error occurred while processing the request. The response contains additional information about the error. |
| Name | Description |
|---|---|
| error | Error information. This parameter is only returned if the request failed.Data type: Object ``` "error": { "message": "String", "detail": "String" } ``` |
| error.message | Error message containing the reason the request failed.Data type: String |
| error.detail | Additional details about why the request failed.Data type: String |
| result | Details about the records that were successfully created.``` "result": { "createdEntitiesCount": {Object}, "receivedIntelligenceRecord": "String" } ``` Data type: Object |
| result.createdEntitiesCount | Count of each type of created entity.``` "createdEntitiesCount": { "indicators": Number, "objects": Number, "observables": Number } ``` Data type: Object |
| result.createdEntitiesCount.indicators | Count of created indicators.Data type: Number |
| result.createdEntitiesCount.objects | Count of created objects.Data type: Number |
| result.createdEntitiesCount.observables | Count of created observables.Data type: Number |
| result.receivedIntelligenceRecord | Identification number of the created inbound intelligence record.Data type: String Table: Inbound Intelligence \[sn\_sec\_tisc\_inbound\_intelligence\] Column: Number |