API REFERENCE v1

Settings

Account callback settings are available. Wallet preferences, forwarding and account profiles remain planned.

On this page

#Account settings

Available

Update the selected-network LTC account callback. Only the fields below are accepted; changing settings does not contact the callback URL.

PATCH/accounts/{account}

Request

HTTP MethodPATCH
Content Typeapplication/json
URLhttps://coinkun.com/api/v1/accounts/{account}
Authorization
transfer-key in the JSON body. JWT remains planned.

Parameter	Type	Description	Required
`account`	string	Account identifier in the URL.	Yes
`currency`	string	Must be ltc on the selected network.	Yes
`transfer-key`	string	Transfer Key of this account. JWT is not implemented.	Yes
`callback`	object or null	Notification method, destination URL and optional merchant metadata.	Yes

curl --request PATCH "https://coinkun.com/api/v1/accounts/${ACCOUNT_ID}" \
  --header 'Content-Type: application/json' \
  --data '{
  "currency": "ltc",
  "transfer-key": "YOUR_TRANSFER_KEY",
  "callback": {
    "url": "https://merchant.example/notify",
    "method": "POST",
    "data": {}
  }
}'

{
  "currency": "ltc",
  "transfer-key": "YOUR_TRANSFER_KEY",
  "callback": {
    "url": "https://merchant.example/notify",
    "method": "POST",
    "data": {}
  }
}

{
  "account": "apr-00000000000000000000000000000001",
  "currency": "ltc",
  "callback": {
    "url": "https://merchant.example/notify",
    "method": "POST",
    "data": {}
  }
}

Illustrative example · Replace YOUR_* and ${VARIABLES} with your own values · Never paste real keys into shared documentation.

#Wallet settings

Planned

Planned wallet preferences use a wallet identifier rather than an internal account identifier. The currency belongs to the wallet itself.

PATCH/wallets/{wallet}

Request

HTTP MethodPATCH
Content Typeapplication/json
URLhttps://coinkun.com/api/v1/wallets/{wallet}
Authorization
Bearer YOUR_ACCESS_TOKEN Planned

Parameter	Type	Description	Required
`wallet`	string	Public wallet identifier.	Yes
`transfer-key`	string	Required unless a supported access token is used.	No
`processing-fee-policy`	string	Intended fixed or percentage fee policy.	No
`callback`	object	Notification configuration.	No
`destinations`	array	Percentage-based forwarding destinations.	No
`destination_rules`	array	Reserved for automatic transfer rules.	No

curl --request PATCH "https://coinkun.com/api/v1/wallets/${WALLET_ID}" \
  --header "Authorization: Bearer ${ACCESS_TOKEN}" \
  --header 'Content-Type: application/json' \
  --data '{
  "transfer-key": "YOUR_WALLET_TRANSFER_KEY",
  "processing-fee-policy": "fixed"
}'

{
  "transfer-key": "YOUR_WALLET_TRANSFER_KEY",
  "processing-fee-policy": "fixed"
}

{
  "wallet": "ltc-00000000000000000000000000000001",
  "currency": "ltc",
  "created": "2026-09-05T12:00:00.000000Z",
  "units": "litoshi",
  "processing-fee-policy": "fixed",
  "fee": "normal",
  "destinations": null,
  "destination_rules": null,
  "callback": null
}

Illustrative example · Replace YOUR_* and ${VARIABLES} with your own values · Never paste real keys into shared documentation.

#Account profile

Planned

Proposed profile fields are grouped under profile rather than exposed as a separate endpoint. They are not inputs to the currently implemented Create Account endpoint.

Field	Type	Meaning
first_name	string	Given name
last_name	string	Family name
email	string	Contact email address
send_updates	boolean	Preference for product updates
country	string	ISO 3166-1 alpha-3 country code
org_type	string	Organization category

#Automatic transfer rules

Planned

Automatic transfers may eventually support balance thresholds and schedules. A complete destination_rules request schema is not published in the reference documentation, so this page does not invent one.

Coinkun API v1 · Reviewed against this checkout
Contract reference: Apirone documentation. Adapted for Coinkun; implementation status is shown above.