ThreatJammer.com User API

Name: ThreatJammer.com User API API
Brand: ThreatJammer.com User API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer Supportbearer96 EndpointsREST

For Agents

Programmatically creates a new private allowlist binded to the user., get the set of private allowlists of the user.. Covers 96 operations with bearer authentication.

Connect the ThreatJammer.com User API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ThreatJammer.com User API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ThreatJammer.com User API API.

Creates a new private allowlist binded to the user.

Get the set of private allowlists of the user.

Update the information of an existing private allowlist of the user.

Delete all the bindings between a user and a private allowlist.

GET STARTED

Start building with ThreatJammer.com User API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ThreatJammer.com User API, keeping it validated and agent-ready.

The public API open to the users. [Read the docs and learn more.](https://threatjammer.com/docs). 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 . The API exposes 96 endpoints secured with bearer authentication.

Use Cases

Patterns agents use ThreatJammer.com User API API for, with concrete tasks.

★ CRM Operations

Use the ThreatJammer.com User API to perform crm operations programmatically. The API provides 96 endpoints covering core functionality including creates a new private allowlist binded to the user., get the set of private allowlists of the user., get the set of private allowlists of the user by resource type..

Call POST /v1/allowlist/private to creates a new private allowlist binded to the user.

Automated Allowlist Management

Automate allowlist operations by combining multiple ThreatJammer.com User API endpoints. Agents can get the set of private allowlists of the user. and then get the set of private allowlists of the user by resource type. in a single workflow.

Call GET /v1/allowlist/private/all to get the set of private allowlists of the user., then verify the result

AI Agent Integration via Jentic

AI agents discover and call ThreatJammer.com User API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'creates a new private allowlist binded to the user.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

96 endpoints — the public api open to the users.

METHOD

PATH

DESCRIPTION

POST

/v1/allowlist/private

Creates a new private allowlist binded to the user.

GET

/v1/allowlist/private/all

Get the set of private allowlists of the user.

GET

/v1/allowlist/private/all/{resource_type}

Get the set of private allowlists of the user by resource type.

GET

/v1/allowlist/private/ip/{address}

Get the different private allowlists where the IP address was found.

GET

/v1/allowlist/private/{allowlist_id}

Get the details of a specific private allowlist of the user.

PUT

/v1/allowlist/private/{allowlist_id}

Update the information of an existing private allowlist of the user.

DELETE

/v1/allowlist/private/{allowlist_id}

Delete all the bindings between a user and a private allowlist.

GET

/v1/allowlist/private/{allowlist_id}/content

Get the content of a private allowlist of the user.

POST

/v1/allowlist/private

Creates a new private allowlist binded to the user.

GET

/v1/allowlist/private/all

Get the set of private allowlists of the user.

GET

/v1/allowlist/private/all/{resource_type}

Get the set of private allowlists of the user by resource type.

GET

/v1/allowlist/private/ip/{address}

Get the different private allowlists where the IP address was found.

GET

/v1/allowlist/private/{allowlist_id}

Get the details of a specific private allowlist of the user.

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ThreatJammer.com User API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'creates a new private allowlist binded to the user.') and Jentic returns the matching ThreatJammer.com User API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct ThreatJammer.com User API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Hubspot

Alternative crm API

Choose Hubspot when you need a different approach to crm operations

Alternative

Salesforce

Alternative crm API

Choose Salesforce when you need a different approach to crm operations

Complementary

Pipedrive

Complementary crm API

Choose Pipedrive when you need a complementary approach to crm operations

Complementary

Zoho

Complementary crm API

Choose Zoho when you need a complementary approach to crm operations

FAQs

Specific to using ThreatJammer.com User API API through Jentic.

What authentication does the ThreatJammer.com User API use?

The ThreatJammer.com User API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I creates a new private allowlist binded to the user. with the ThreatJammer.com User API?

Yes. Use the POST /v1/allowlist/private endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the ThreatJammer.com User API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I creates a new private allowlist binded to the user. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'creates a new private allowlist binded to the user.'. Jentic returns the matching ThreatJammer.com User API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the ThreatJammer.com User API have?

The ThreatJammer.com User API exposes 96 endpoints covering allowlist, asn, assess operations.