Referral APIs

InkyPump has two related records:

A global referral code owned by a wallet.
A permanent, chain-scoped fee-earning binding from a referred wallet to a code.

An on-chain Referral event is not a substitute for the permanent fee-earning binding.

Referral code

Method	Route	Purpose
`POST`	`/api/referral/challenge`	Get a short-lived message for code creation
`POST`	`/api/referral/create`	Submit wallet signature and create the code
`GET`	`/api/referral/:address?chainId=`	Read code ownership, points, and historical referred transaction hashes
`GET`	`/api/referral/check/:code`	Check a code

Code creation is challenge-based. It is not Bearer-token authentication.

Permanent fee-earning binding

Chain	Challenge	Accept	Dashboard	Activity
Ink	`POST /api/referrals/ink/challenge`	`POST /api/referrals/ink/accept`	`GET /api/referrals/ink/dashboard/:address`	`GET /api/referrals/ink/activity/:address`
Robinhood	`POST /api/referrals/robinhood/challenge`	`POST /api/referrals/robinhood/accept`	`GET /api/referrals/robinhood/dashboard/:address`	`GET /api/referrals/robinhood/activity/:address`

Ink also exposes:

GET /api/referrals/ink/eligibility/{address}?chainId=57073

Ink binding flow

Request a challenge:

POST /api/referrals/ink/challenge?chainId=57073
Content-Type: application/json

{
  "chainId": 57073,
  "walletAddress": "0x...",
  "referralCode": "CODE123"
}

The response includes challengeId, expiresAt, signingDomain, normalized referralCode, nonce, and the exact message to sign. After personal_sign, submit all challenge fields unchanged:

POST /api/referrals/ink/accept?chainId=57073
Content-Type: application/json

{
  "chainId": 57073,
  "walletAddress": "0x...",
  "referralCode": "CODE123",
  "challengeId": "...",
  "nonce": "...",
  "signingDomain": "inkypump.com",
  "expiresAt": "...",
  "signature": "0x..."
}

The binding is permanent. The API rejects self-referral, an already-bound wallet, expired/consumed challenges, mismatched data, and invalid signatures.

Accounting fields

Dashboard responses keep states separate, including pending, uncertain, finalized, accrued, claimable, reserved, and paid amounts. Do not collapse all of them into “earned.” Keep raw amount strings and dataThroughBlock.

Call these endpoints from your backend. They use chain context, rate limits, and no-store responses.

InkyPump Contracts

MCP Server

API Documentation

InkyPump API

InkySwap API

Referral code

Permanent fee-earning binding

Ink binding flow

Accounting fields

​Referral code

​Permanent fee-earning binding

​Ink binding flow

​Accounting fields

Referral code

Permanent fee-earning binding

Ink binding flow

Accounting fields