Skip to main content

API Routes

Seqlense MABU API Documentation

The Seqlense MABU API provides routes for registering, monitoring, and retrieving history of blockchain addresses.

Authentication

All API requests must include the API key in the Authorization header.

Header format:

Authorization: token <uuid-v4>

Address

1. Add Address

Registers a new customer on-chain address, submits it for the initial scan, and enables continuous monitoring.

Endpoint:

POST /api/v1/mabu/address/add

Request Body (JSON):

{
  "address": "0x1234567890abcdef...", 
  // bulk push can be used by using an array of address
  // "address": ["0x1234567890abcdef...", "0x1234567890abcdef...", "0x1234567890abcdef..." ...], 
  "custom_field": "optional_custom_value", // used for Seqlense Mabu Identity & your own db link
  "scan_frequency": 0, // optional
}

About scan frequency : If scan frequency is set to 0, default organization frequency will be used, if set, the scan frequency will happen evey {value} days.

Response:

  • Returns confirmation of registration and scan status.

2. Update Address

Update an address custom_field or scan_frequency

Endpoint:

POST /api/v1/mabu/address/update

Request Body (JSON):

 

{
    "address": "0x1234567890abcdef...",
    "custom_field": "test", // optionnal new value
    "scan_frequency": 7 // optionnal new value
}

Response:

  • Returns confirmation of update and scan status.

3. Disable Address

Disable address from the list of recurrent scan system

Endpoint:

PUT /api/v1/mabu/address/disable?address=0x1234567890abcdef...

Response:

  • Returns confirmation of address status.

4. Enable Address

Enable address from the list of recurrent scan system

Endpoint:

PUT /api/v1/mabu/address/enable?address=0x1234567890abcdef...

Response:

  • Returns confirmation of address status.

Identity

Organization

 

Notes

  • addr (string): Blockchain address to be registered, removed, or queried.

  • custom_field (string, optional): A custom identifier or metadata for the address.

  • All requests require valid authorization headers.

  • Responses are in JSON format.

Back to top