Automate ThreatJammer.com User
HumDay reads ThreatJammer.com User’s own published API description and derives 96 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What ThreatJammer.com User is
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 do
What HumDay can do in ThreatJammer.com User
35 documented operations change something in ThreatJammer.com User.
- POSTCreates a new private denylist binded to the user.
/v1/denylist/private - POSTCreates a new private allowlist binded to the user.
/v1/allowlist/private - POSTCreate an origin token of the user in the region.
/v1/origin_token/new - PUTAdd or remove content of a private denylist of the user.
/v1/denylist/private/{denylist_id}/content - PUTAdd or remove content of a private allowlist of the user.
/v1/allowlist/private/{allowlist_id}/content - POSTGet the information found in a set of User Agents.
/v1/ua - PUTUpdate the configuration of an origin of the user in the region.
/v1/origin - DELETEDelete an origin token of the user in the region.
/v1/origin_token - POSTGet the information of an origin token of the user in the region.
/v1/origin_token - DELETEDelete all the bindings between a user and an denylist.
/v1/denylist/public/{denylist_id} - PUTToogle the status of an deny list.
/v1/denylist/public/{denylist_id} - DELETEDelete all the automatically reported IP addresses by the user.
/v1/denylist/reported/ip/all - DELETEDelete all the bindings between a user and a private denylist.
/v1/denylist/private/{denylist_id} - PUTUpdate the information of an existing private denylist of the user.
/v1/denylist/private/{denylist_id} - DELETEDelete all the bindings between a user and an allowlist.
/v1/allowlist/public/{allowlist_id} - PUTToogle the status of an allow list.
/v1/allowlist/public/{allowlist_id} - POSTGet the information found in the set of User Agents uploaded.
/v1/ua/csv - DELETEDelete all the bindings between a user and a private allowlist.
/v1/allowlist/private/{allowlist_id} - PUTUpdate the information of an existing private allowlist of the user.
/v1/allowlist/private/{allowlist_id} - POSTGet the current cookie ID and IP address status of the origin of user in the region.
/v1/origin/status - PUTEnable a disabled origin token of the user in the region.
/v1/origin_token/enable - PUTDisable a enabled origin token of the user in the region.
/v1/origin_token/disable - DELETEDelete the automatically reported IP address by the user.
/v1/denylist/reported/ip/{ip_address} - PUTToogle the status of the origin in a deny list.
/v1/denylist/public/{denylist_id}/origin - PUTToogle the status of the origin in a deny list.
/v1/denylist/private/{denylist_id}/origin - PUTToogle the status of the origin in an allow list.
/v1/allowlist/public/{allowlist_id}/origin - DELETEDelete all the content of a private denylist of the user.
/v1/denylist/private/{denylist_id}/content - PUTToogle the status of the origin in an allow list.
/v1/allowlist/private/{allowlist_id}/origin - DELETEDelete all the content of a private allowlist of the user.
/v1/allowlist/private/{allowlist_id}/content - POSTGet the geolocation data of the IP addresses set.
/v1/geo - POSTGet the geolocation data of all the IP addresses uploaded.
/v1/geo/csv - POSTGet the risk score of all IP address passed in the body and other data signals.
/v1/assess/ip - POSTGet the IPv4 or IPv6 prefix of the CIDR given.
/v1/asn/prefix - POSTGet the IPv4 or IPv6 prefix of the CIDR given.
/v1/datacenter/prefix - POSTGet the risk score of all IP address uploaded and other data signals.
/v1/assess/ip/csv
What HumDay can read from ThreatJammer.com User
These are the operations a schedule or a trigger can watch.
- GETGet the list of automatically reported IP addresses by the user.
/v1/denylist/reported/ip - GETGet the set of private denylists of the user.
/v1/denylist/private/all - GETGet the set of private allowlists of the user.
/v1/allowlist/private/all - GETGet the information of the user's token in the region.
/v1/token - GETGet the information of an origin of the user in the region.
/v1/origin - GETGet the details of a specific private denylist of the user.
/v1/denylist/private/{denylist_id} - GETGet the details of a specific private allowlist of the user.
/v1/allowlist/private/{allowlist_id} - GETGet the full information of all the source lists for the subscription level given.
/v1/source/ip - GETGet the list of all the datasets available in the platform.
/v1/dataset/ip - GETGet the information of the origins of the user in the region.
/v1/origin/all - GETGet the tracking cookie ID status of the origin of the user in the region.
/v1/origin/cookies - GETGet the code snippets of an origin of the user in the region.
/v1/origin/scripts - GETGet the information of the origin tokens of the user in the region.
/v1/origin_token/all - GETGet the address status of the origin of the user in the region.
/v1/origin/addresses - GETGet the details of an automatically reported IP addresses by the user.
/v1/denylist/reported/ip/{ip_address} - GETGet the set of private denylists of the user by resource type.
/v1/denylist/private/all/{resource_type} - GETGet the set of private allowlists of the user by resource type.
/v1/allowlist/private/all/{resource_type} - GETGet the set of public denylists of a user by resource type.
/v1/denylist/public/owned/{resource_type} - GETGet the set of public allowlists of a user by resource type.
/v1/allowlist/public/owned/{resource_type} - GETGet the content of a private denylist of the user.
/v1/denylist/private/{denylist_id}/content - GETGet the list of status of an object in a registry.
/v1/asn/status/all - GETGet the content of a private allowlist of the user.
/v1/allowlist/private/{allowlist_id}/content - GETGet the list of the Regional Internet Registries (RIRs) entities worldwide.
/v1/asn/registry/all - GETGet the set of public denylists.
/v1/denylist/public/all - GETGet the set of public allowlists.
/v1/allowlist/public/all - GETGet the set of owned denylists.
/v1/denylist/public/owned - GETGet the list of different status available in the platform.
/v1/origin/status/details - GETGet the information found in an User Agent.
/v1/ua/{user_agent_urlencoded} - GETGet the set of owned allowlists.
/v1/allowlist/public/owned - GETGet the information of the Operating System of a user agent.
/v1/ua/os/{code} - GETGet the information of the type of a user agent.
/v1/ua/type/{code} - GETGet the information of the device of a user agent.
/v1/ua/device/{code} - GETGet the information of the family of a user agent.
/v1/ua/family/{code} - GETGet the information of the vendor of a user agent.
/v1/ua/vendor/{code} - GETGet the full information of the source list given as argument.
/v1/source/ip/{source} - GETGet the list of IPv4 and IPv6 prefixes of the AS number given.
/v1/asn/{number}/prefixes - GETGet the details of the denylist.
/v1/denylist/public/{denylist_id} - GETGet the details of the allowlist.
/v1/allowlist/public/{allowlist_id} - GETGet the list of IPv4 and IPv6 prefixes of the Datacenter given.
/v1/datacenter/{datacenter_id}/prefixes - GETGet the activity information of the token in the region.
/v1/token/activity - GETGet a log event.
/v1/log/ip/id/{logchange_id} - GETGet the different public denylists where the IP address was found.
/v1/denylist/public/ip/{address} - GETGet the different public allowlists where the IP address was found.
/v1/allowlist/public/ip/{address} - GETGet the different denylists where the IP address was found.
/v1/denylist/private/ip/{address} - GETGet the different private allowlists where the IP address was found.
/v1/allowlist/private/ip/{address} - GETGet the Autonomous System details of the AS number given.
/v1/asn/{number} - GETGet the set of public denylists by resource type.
/v1/denylist/public/all/{resource_type} - GETGet the set of public allowlists by resource type.
/v1/allowlist/public/all/{resource_type} - GETGet the geo location data of the IP address.
/v1/geo/{ip_address} - GETGet the Datacenter details of datacente given.
/v1/datacenter/{datacenter_id} - GETGet the type of clients of the trafffic of the origin.
/v1/origin/client/analysis - GETGet the traffic analysis of the origin.
/v1/origin/traffic/analysis - GETGet the information of a status given.
/v1/asn/status/{code} - GETGet the detailed information of the dataset queried.
/v1/dataset/ip/{name} - GETGet the IPv4 or IPv6 prefix of the IP address given.
/v1/asn/ip/{ip_address} - GETGet the information of a Regional Internet Registries (RIRs) given.
/v1/asn/registry/{code} - GETGet the changes logged in the different datasets of an IP address.
/v1/log/ip/{ip_address} - GETGet a risk score of the IP address and different data signals.
/v1/assess/ip/{ip_address} - GETGet the IPv4 or IPv6 prefix of the IP address given.
/v1/datacenter/ip/{ip_address} - GETGet the information of the source list given for a specific time range.
/v1/source/ip/{source}/range/{time_range} - GETGet detail of a status available in the platform.
/v1/origin/status/detail/{status_id}
How automating ThreatJammer.com User works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live ThreatJammer.com User account.
- Grant access, then go live. You approve the specific ThreatJammer.com User operations it may use — and only those.
Questions about ThreatJammer.com User automation
- Can HumDay connect to ThreatJammer.com User?
- Yes. HumDay reads ThreatJammer.com User's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 96 operations are documented.
- Do I need to write code to automate ThreatJammer.com User?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your ThreatJammer.com User account.
- What can HumDay do in ThreatJammer.com User?
- 35 of the 96 documented operations change something in ThreatJammer.com User, and 61 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my ThreatJammer.com User account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to ThreatJammer.com User is held behind that approval.
Where this came from
The operations above are read from a published API description for ThreatJammer.com User at dublin.api.threatjammer.com/openapi.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.