API archive entry · source-reported

ThreatJammer.com User API

The public API open to the users. Read the docs and learn more.. ## General information ### Description Threat Jammer supports two end-user REST APIs: the User API and the Report API. The end-user uses the User API to interact with the different databases, heuristics, and machine learning processes. Devices use the Report API to interact with Threat Jammer. This document will explain how to use the User API and interact with the different services, create a token, interpret the quota information, and create the HTTP request to interact with the User API. ### Authentication The API is protected by a **Bearer authentication** schema. **Bearer authentication** (also called **token authentication**) is an HTTP authentication scheme that involves security tokens called bearer tokens. It is used to authenticate the user. All the different endpoints expect a `Bearer` token in the `Authorization` header. Example: ``` curl -X 'GET' 'https://dublin.api.threatjammer.com/test' -H 'accept: application/json' -H 'Authorization: Bearer YOUR_API_KEY' ``` You can obtain a token after registering on the ThreatJammer.com website for free. ### Region specific tokens All the `Bearer` tokens contain info

Provider / source website

Archive history

This history reflects directory observations and owner review, not a provider release log.

  1. First observed: Sep 20, 2026
  2. Last directory-field change: Sep 20, 2026
  3. Current source observation: Sep 20, 2026

Published source events

added

Sep 20, 2026 · Added from an approved API directory.

Where to check product changes

Use the provider documentation and status channels for releases, breaking changes, and outages.

Source reference

APIs.guru OpenAPI Directory

This page separates source-reported facts from questions that need live provider verification.