@reaqta/hive-api

ReaQta-Hive API Client (JS)

A JavaScript client for interacting with the ReaQta-Hive API.

Install via NPM:

$ npm install @reaqta/hive-api

Quick Start

To quickly interact with the API, and experiment with this client, we suggest you first clone this repository.

Next, create an Application in your dashboard, and record its id and secret. You will need these to authenticate against the api.

Copy the .env.example file in the project root, like so:

$ cp .env.example .env

Then, add your Application Id, Application Secret, and API url (including the base path to the api routes!) to the .env file, like so:

REAQTA_API_URL="https://my-dashboard.secure.org:14643/rqt-api"
REAQTA_API_APP_ID="19189d32-af70-45c3-bbce-a1c2d27ddc74"
REAQTA_API_SECRET_KEY="trustno1"

Afterwards, you can modify and run the scripts available in the recipes folder. E.g.,

$ node recipes/alerts-polling

Once you configure your .env file, an API client will be automatically created for you in the repl. (See: REPL, below.)

Documentation

Comprehensive API documentation for expected response data, as well as API search parameters, can be found on your ReaQta-Hive installation.

Documentation (including some tutorials) for this API client exists in the docs folder. You can serve the client documentation locally by running:

# Install dependencies
$ npm install
# Generate docs
$ npm run docs
# Serve the docs locally
$ npm run docs:serve

The docs will then be reachable at http://localhost:61108

REPL

This repository also includes a basic REPL to play with the API client.

To start the repl:

• Install dependencies (npm install in the project root)
• Configure your .env file with your API credentials
• Run the repl script (npm run repl)

If you have defined the necessary environment variables in your .env file, the repl will automatically instantiate an API client for you under the variable client.

Usage Notes

Before using the api, it's good to know a few of its characteristics.

Eventual Consistency

The ReaQta-Hive backend is eventually consistent. What this means in practice is that the resources you create might not be immediately available for retrieval. (They will likely show up after a few hundred milliseconds.)

Some workflows may require you to create a new resource, and then directly update some of its properties. In this scenario, you will want to add retries when you retrieve a newly created resource, in the event that the first few requests for the resource return a 404.

Authentication

The ReaQta-Hive API uses JSON Web Tokens (JWTs) to authenticate. As of writing, JWTs issued by the API are typically valid for 15 minutes.

The API client handles generating and refreshing these tokens automatically, so it is only necessary to provide your application's id and secret when you instantiate the client.

If you're interested in building your own api client, in javascript or any other language, feel free to treat the code in lib/authentication as a reference implementation for handling authentication.

Endpoint Isolation

Isolating non-Windows endpoints does not work with the current version of the API. Your request will timeout, and you will receive a 504.