API Reference

Integrate GOBERIN's high-performance transaction engine into your external systems using our secure, low-latency REST API architecture.

API Base Endpoint

Status: Active

Network_Vector

Analyzing...

Engine_Uptime

Server_IP_Node

---.---.---.---

Client_Entry_Point

---.---.---.---

Last_Handshake: PENDING

Core_Metrics

Node_Ver N/A

Platform N/A

Memory_Usage 0MB

Signal_Latency

Stable / Optimal

Authentication Methods

All interface requests require high-clearance authentication headers. For mission-critical server-to-server integrations, we mandate the usage of the API Key method.

Method A: API_KEY

X-API-Key: {TOKEN}

Method B: JWT_BEARER

Authorization: Bearer {JWT}

Product List

GET_METHOD /api/trx/products

Retrieve a comprehensive list of available products, categories, and providers. Price calculations are already synchronized based on your current pricing parameters.

Parameter	Default Value	Description
page	1	Page number for pagination.
limit	50	Number of items displayed.
categoryId	NULL	Filter node by Category UUID.

Example Response

{
    "success": true,
    "data": [
        {
            "id": "ecc83b71-...",
            "sku": "TRH9M10",
            "name": "Tri Happy High_Frequency",
            "totalPrice": 35000
        }
    ],
    "pagination": {
        "total": 1,
        "totalPages": 1,
        "page": 1,
        "limit": 50
    }
}

Category List

GET_METHOD /api/trx/categories

Connect your system with all available product categories (e.g., Pulsa, E-Wallet, Electricity). Use category IDs to filter results.

GET_METHOD /api/trx/providers

Query Parameters

Field	Type	Required
categoryId	UUID_STRING	FALSE

{
    "success": true,
    "data": [
        {
            "id": "dc160364-...",
            "name": "Operator Delta-T",
            "slug": "delta-t-operator"
        }
    ]
}

Prepaid API

POST_METHOD /api/trx/prepaid

Execute High-Frequency Prepaid Transactions (Pulsa, Data, E-Wallet). Operations can be triggered via productId (UUID) or the human-readable SKU identifier.

Request Parameters

Field Name	Mandatory
customerNo	TRUE
sku / productId	TRUE
referenceId	FALSE

Example Request

{
    "sku": "TRH9M10-DELTA",
    "customerNo": "0812XXXXXXXX",
    "referenceId": "TRX_NODE_99"
}

Postpaid API

Handle bill payments (PLN Pasca, BPJS, PDAM). The flow requires an Inquiry to retrieve the bill amount before execution.

POST_INQUIRY /api/trx/postpaid/inquiry

Inquiry_Parameters

Field	Required
customerNo	TRUE
sku / productId	TRUE

{
    "sku": "PLNPASCA",
    "customerNo": "53XXXXXXXXXX"
}

POST_PAYMENT /api/trx/postpaid/pay

Payload is identical to Inquiry. Use the same identifiers to execute settlement.

Integration Bridge: BukaOlshop

POST_METHOD /api/trx/bukaolshop

A seamless bridge for the BukaOlshop ecosystem. This integration handles cross-system balance deduction, inquiry validation, and automated refund logic within a single request execution.

BRIDGE_PARAMETER_SET

tokenUser | idUser

BukaOlshop High-Security Auth Pair.

User-Level 6-Digit PIN Authentication.

// This interface is highly secure.
// Ensure tokens remain within
// encrypted memory spaces.

{
    "tokenUser": "hash_alpha_92...",
    "idUser": "user_node_42",
    "pin": "XXXXXX"
}

Signals & History

GET_HISTORY /api/trx/history

Filter_Params

Param	Description
idUser	Filter by BukaOlshop ID
tokenUser	Filter by User Token
limit	Default: 50

{
    "success": true,
    "data": [
        {
            "id": "node_alpha_1",
            "status": "SUCCESS",
            "sn": "SN_992182",
            "updatedAt": "2024-05-27T..."
        }
    ]
}

GET_STATUS /api/trx/status/:id

Retrieve granular details of a specific transaction node using its internal UUID.

{
    "success": true,
    "data": {
        "id": "trx_node_uuid",
        "status": "SUCCESS",
        "sn": "1234567890",
        "notes": "Transaction_Verified",
        "updatedAt": "2026-06-10T10:05:31.160Z"
    }
}

Signal Callbacks (Webhooks)

Nexus notifies your destination node of transaction status transitions via outbound asynchronous POST signals. Ensure your secure endpoint is reachable and returns a 200_OK magnitude signal.

Outbound Payload schematic

{
    "ref_id": "uuid-nexus-core",
    "status": "SUCCESS",
    "sn": "1234567890",
    "message": "Transaksi Sukses",
    "timestamp": "2026-06-10T10:05:31.160Z"
}

SECURITY_MANDATE: Validate Signal Origin by checking the IP Source against Nexus White-List Protocol before committing data changes.