RootsHive Collection

An all in one platform for your Business

Welcome to the Rootshive Developer Documentation where you’d find help and necessary guidance through your integrations ranging from KYT, Cross-Border Transfers, Payouts, Insights, Metrics, Payrolls, Clockin systems, invoice and other business tools. We Simplify and Automate your Business Processes

– all in one place.

Start here

SThe Rootshive API provides extensive access to the features available on our dashboard, enabling you to leverage them for your own application. To get started, you must first create a Rootshive account on https://therootshive.com and obtain the required API keys for all Roothsive integrations. Please note that the Rootshive API is secured through Basic Authentication or OAuth (Bearer Tokens).

Authentication

Rootshive's core security protocol is OAuth 2.0, which authenticates API requests via associated API keys that can be managed directly from the dashboard. Rootshive provides an APP id and a live Key, that is used together with a secret key to generate a basic token and a secret key that should be kept confidential and stored exclusively on the user's servers

To access Monnify endpoints, an access token is required, which is obtained by submitting a request to the login endpoint using the OAuth2 protocol. When making the request, the authorization header should be formatted as
Basic base64(appid:rhlive)

Webhooks

Webhooks is an API concept that enables applications to automatically communicate with each other without constant polling. Rootshive integration sends notifications to a URL on the merchants’ server when specific events such as when payments are being received or when settlements are made to your account, allowing further actions such as sending an email or providing value to the user. Rootshive supports webhooks for various events like card transactions, settlement and disbursement completion, and refunds. To implement webhooks on your Rootshive integration, it is recommended to follow certain best practices such as validating transaction hash, whitelisting Rootshive's IP address, checking for duplicate notifications, and processing complex logic after acknowledging receipt of the notification with a 200 HTTP status code. These practices ensure the integrity and security of the payload, prevent unauthorized requests, avoid redundant processing, and prevent time-out issues.

Structure and Sample

A typical event notification structure is of the format:

{
	"eventType": "type_of_event",
	"eventData": {
		"prop1": "value1",
		"prop2": "value2"
	}
}

IP Whitelisting

it is crucial to provide Rootshive with your server's IP address for whitelisting purposes, so that only withdrawal requests from that specific IP address(es) are authorized.

Summary