Retrieving Data from the TAXII 2.1 Server (App Version 1.0)
  • 02 Sep 2022
  • 1 Minute to read
  • Dark
    Light

Retrieving Data from the TAXII 2.1 Server (App Version 1.0)

  • Dark
    Light

Article summary

To retrieve data from the ThreatConnect TAXII™ 2.1 server via the TAXII REST API, you must use a TAXII user account. If you do not have a TAXII user account, see Creating a TAXII User for the TAXII 2.1 Server.

Authentication

The TAXII REST API uses basic authentication, which is completed using the username and password of your TAXII user account.

Required Headers

The Accept header must be set to application/taxii+json;version=2.1.

Available Endpoints

Refer to Table 1 for a description of each available API endpoint on the ThreatConnect TAXII 2.1 server and supported HTTP method for each endpoint.

 

EndpointHTTP MethodDescription
/tc_taxii/GETRetrieves information about the ThreatConnect TAXII 2.1 server
/tc_taxii/collections/GETRetrieves information about all collections available on the ThreatConnect TAXII 2.1 server
/tc_taxii/collections/{collection_id or org_name}/GETRetrieves information about a specific collection available on the ThreatConnect TAXII 2.1 server
/tc_taxii/collections/{collection_id or org_name}/manifest/GETRetrieves manifest information about the contents of a specific collection available on the ThreatConnect TAXII 2.1 server
/tc_taxii/collections/{collection_id or org_name}/objects/GETRetrieves all objects from a specific collection available on the ThreatConnect TAXII 2.1 server
/taxii2/GETRetrieves information about the TAXII 2.1 server and available API Roots

Available Parameters

Parameters included in common STIX™ 2.1 frameworks are supported for the API endpoints listed in Table 1.

Example Requests and Responses

Example requests and responses for each endpoint listed in Table 1 are available at docs.threatconnect.com/en/latest/rest_api/taxii/taxii_2.1.html.


ThreatConnect® is a registered trademark of ThreatConnect, Inc.
STIX™ and TAXII™ are trademarks of The MITRE Corporation.

20103-04 v.05.A


Was this article helpful?