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
  "is_enabled": bool, // 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.

"is_enabled" is used to push an address into monitoring but block it from initial scan an other scan using the "is_enable: false"

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

3.1 Disable One address

Endpoint:

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

Response:

  • Returns confirmation of address status.

3.2 Disable multiple addresses

Endpoint:

PUT /api/v1/mabu/address/disable

Request Body (JSON):

{
    "address": ["0x1234567890abcdef...", "..."] //array of adr
}

Response:

  • Returns confirmation of address status.

4. Enable Address

4.1 Enable One address

Endpoint:

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

Response:

  • Returns confirmation of address status.

4.2 Enable multiple addresses

Endpoint:

PUT /api/v1/mabu/address/enable

Request Body (JSON):

{
    "address": ["0x1234567890abcdef...", "..."] //array of adr
}

Response:

  • Returns confirmation of address status.

5. Force new scan

Enable address from the list of recurrent scan system

Endpoint:

POST /api/v1/mabu/address/scan

Request Body (JSON):

{
    "address": "0x1234567890abcdef..." // address to scan,
    "type": "type_value" // scan type 
}

Scan type can be:

"standard",
"insider_trading",
"pump_and_dump",
"smurfing",
"wash_trading",
"ai_analysis"

"Standard" scan is a scan where all other scan are executed

Response:

  • Returns confirmation scan start

  • Returns the scan_uuid

Web url can be forged:

Wallet detail: https://seqlense.com/mabu/?q={wallet_adr}

Scan detail: https://seqlense.com/mabu/scan?id={scan_id}

Identity

Seqlense Mabu Identity is a simple way of mapping and grouping data from multiple wallets into a single "Identity" (legal person or company)

1. Create Identity

Create a new identity in Seqlense Mabu Identity

Endpoint:

POST /api/v1/mabu/identity/create

Request Body (JSON):

{
    "full_name": "Alice", // legal name 
    "note": "new short note" // a simple note about the identity
}

Response:

  • Returns confirmation of registration AND Identity Id (who is a UUIDV4)

2. Update Identity

Update an identity in Seqlense Mabu Identity

Endpoint:

POST /api/v1/mabu/identity/update?identity=d0cc61eb-f3... // with the identity id

Request Body (JSON):

{
    "full_name": "Bob", // optionnal new legal name 
    "note": "this is a note" // optionnal new simple note about the identity
}

Response:

  • Returns confirmation of update

3. Delete Identity

Delete an identity in Seqlense Mabu Identity

Endpoint:

DEL /api/v1/mabu/identity/delete?identity=d0cc61eb-f3... // with the identity id

Response:

  • Returns confirmation of suppression

Endpoint:

POST /api/v1/mabu/identity/link

Request Body (JSON):

{
    "user_uuid": "a290427-f3...", // Identity ID
    "identifier": "test" // mapped address custom field value
}

Response:

  • Returns confirmation of new link

Endpoint:

POST /api/v1/mabu/identity/unlink

Request Body (JSON):

{
    "user_uuid": "a290427-f3...", // Identity ID
    "identifier": "test" // mapped address custom field value
}

Response:

  • Returns confirmation of deleted link

List all matching rules for an identity

Endpoint:

GET /api/v1/mabu/identity/list?user=a290427f-f3... // with Identity Id

Response (JSON):

{
    "status": "identity list",
    "data": [
        "link1",
        "link2",
         ....
    ]
}

6. Identity Map

Show Mapping identity address

Endpoint:

GET /api/v1/mabu/identity/map?user=a290427f-f3... // with Identity Id

Response (JSON):

{
    "user_uuid": "a290427f-f3......",
    "data": [
        {
            Wallet_detail 1
        },
        {
            Wallet_detail 2
        }
      ...
    ]
}

Organization

1. Update Scan Frequency

Update the default scan frequency for your registered address

Endpoint:

POST /api/v1/mabu/organization/default-scan-frequency

Response:

  • Returns confirmation of update and scan status.

Alerts

1. Get alert detail

Get the alert detail with the alert ID

Endpoint:

GET /api/v1/mabu/alert/detail?alert_id=000000-00....

Response (JSON):

{
    "status": "alert detail",
    "data": {
        "alert_uuid": "00000....",
        "org_id": 0, // your seqlense org id
        "address": "0x1234567890abcdef......",
        "scan_type": "smurfing",
        "title": "Smurfing detected with score 0.825",
        "scan_uuid": "00000....",
        "alert_time": "2025-10-01T08:00:00Z",
        "is_read": true // is this alert aknowledge ?
    }
}

2. Acknowledging an alert

Acknowledge an alert by his id

Endpoint:

PUT /api/v1/mabu/alert/ack?alert_id=000000-00....

Response:

New status of the alert

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