-
Alert Rule Schema
JupiterOne Alert Rule Schema A rule uses the results of one or more queries to execute one or more actions. The basic alert workflows are described here: JupiterOne Alert Rule configuration documentation. You can also directly edit the JSON that defines a rule for more advanced workflow execution. Configuring a Rule *…
-
Compliance API Endpoints
This article contains a list of compliance actions from the JupiterOne UI that a user can perform using the GraphQL API endpoint. See the JupiterOne Platform API for an introduction to the JupiterOne API. Some key things to note: * Most of the compliance-related data is exposed in one large GraphQL graph. The sections in…
-
Creating User and Account API Keys
API keys enable users to use the J1 APIs in queries and with integrations. You can enable the use of API keys for a group of users and create API keys for your organization account. Enable User-Level API Key Access You must have the Administrator permission to enable API key access. To enable API key access for a group of…
-
J1QL Query Rate Limiting
J1QL queries executed via the J1 public API are rate-limited separately from GraphQL API invocations. Each J1QL query consumes one request token. All queries executed via the J1 public API count towards the rate limit. This count includes user-initiated application queries (such as search and J1 Insights) and queries via…
-
JupiterOne Alert Rule Schema
A rule uses the results of one or more queries to execute one or more actions. The basic alert workflows are described here: JupiterOne Alert Rule configuration documentation. You can also directly edit the JSON that defines a rule for more advanced workflow execution. Configuring a Rule * Navigate to the JupiterOne alert…
-
JupiterOne API
You can use Postman with the JupiterOne API to import and export data. Examples of requests you can make after you have exported your J1 data such as saved queries to Postman are available. The JupiterOne platform exposes a number of public GraphQL endpoints. Base URL: https://graphql.us.jupiterone.io * For query and graph…
-
JupiterOne Bulk Upload Schema
IMPORTANT: Bulk upload triggers a data synchronization process that automatically updates or deletes entities/relationships as needed. Previously existing entities/relationships within the same scope that no longer exist in the latest upload will be marked for deletion. Therefore, the upload file should always include the…
-
JupiterOne GraphQL API Rate Limiting
Rate limiting is a technique to limit network traffic to avoid exhausting system resources. Rate limits are described in terms of tokens and the token-replenishment rate. Various actions performed using the JupiterOne public API deplete tokens and tokens are replenished at a predictable rate. If there are insufficient…
-
JupiterOne Node.js Client and CLI
JupiterOne is a data driven platform. It is easy to add your own data that is not covered by out-of-the-box managed integrations. We provide a node.js API client wrapper and a CLI utility on Github. The CLI supports uploading entities in either JSON or YAML format. This guide - Using JupiterOne as a central repository for…
-
Using Postman with the JupiterOne API
You can use Postman with the JupiterOne API to import and export data. The following are examples of requests you can make after you have exported your J1 data such as saved queries to Postman. { "info": { "_postman_id": "450bcc28-7b47-4190-aefd-79144b3ce4b8", "name": "JupiterOne Public GraphQL", "schema":…
.png)