API REFERENCE v1

Authorization

Planned token-based access for protected account and wallet operations.

On this page

#JWT tokens request

Planned

Intended token exchange using an account or wallet identifier and its Transfer Key. Dashboard unlocking is already separate application functionality; it does not implement this API.

POST/auth/login

Request

HTTP MethodPOST
Content Typeapplication/json
URLhttps://coinkun.com/api/v1/auth/login

Parameter	Type	Description	Required
`login`	string	Account or wallet identifier.	Yes
`password`	string	Transfer Key belonging to that identifier.	Yes

curl --request POST "https://coinkun.com/api/v1/auth/login" \
  --header 'Content-Type: application/json' \
  --data '{
  "login": "apr-00000000000000000000000000000001",
  "password": "YOUR_TRANSFER_KEY"
}'

{
  "login": "apr-00000000000000000000000000000001",
  "password": "YOUR_TRANSFER_KEY"
}

{
  "login": "apr-00000000000000000000000000000001",
  "access-token": "YOUR_ACCESS_TOKEN",
  "refresh-token": "YOUR_REFRESH_TOKEN"
}

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

#Access token refresh

Planned

Planned replacement of an expired access token using a refresh token.

POST/auth/refresh-token

Request

HTTP MethodPOST
Content Typeapplication/json
URLhttps://coinkun.com/api/v1/auth/refresh-token
Authorization
Bearer YOUR_REFRESH_TOKEN Planned

Parameter	Type	Description	Required
`Authorization`	header	Bearer YOUR_REFRESH_TOKEN; this operation requires a refresh token, not an access token.	Yes

curl --request POST "https://coinkun.com/api/v1/auth/refresh-token" \
  --header "Authorization: Bearer ${REFRESH_TOKEN}"

{
  "login": "apr-00000000000000000000000000000001",
  "access-token": "YOUR_NEW_ACCESS_TOKEN",
  "refresh-token": "YOUR_NEW_REFRESH_TOKEN"
}

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

#Logout request

Planned

Planned invalidation of an API authentication session.

POST/auth/logout

Request

HTTP MethodPOST
Content Typeapplication/json
URLhttps://coinkun.com/api/v1/auth/logout
Authorization
Bearer YOUR_ACCESS_TOKEN Planned

Parameter	Type	Description	Required
`Authorization`	header	Bearer YOUR_ACCESS_TOKEN for the session to invalidate.	Yes

curl --request POST "https://coinkun.com/api/v1/auth/logout" \
  --header "Authorization: Bearer ${ACCESS_TOKEN}"

{}

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

#Access to protected endpoints

Planned

The intended compatibility contract supports a Transfer Key parameter or an access-token bearer header on protected operations. Keep keys and tokens out of frontend bundles, source control and logs.

Credential	Placement	Intended use
Transfer Key	transfer-key parameter	Direct authorization of a protected account or wallet operation
Access token	Authorization bearer header	Authenticated API operations
Refresh token	Authorization bearer header	Only the token refresh endpoint

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