Authentication
Last updated
Last updated
To ensure secure access to the Nami Exchange API, all requests must be authenticated using API keys. Follow the steps below to , complete , , and .
You'll need a Nami Exchange account to use the API. Follow these steps to register:
Visit the Registration page: Go to .
Fill out the Registration form: Provide the necessary information, including email address, and password.
Verify your Email: After submitting the registration form, check your email for a verification link. Click the link to verify your email address.
Log in: Once your email is verified, log in to your account using your credentials.
KYC (Know Your Customer) verification helps ensure a secure trading environment. Here's how to complete it:
Locate KYC verification: Navigate to your account settings and find the dedicated KYC verification section.
Submit required documents: Provide the necessary documentation, such as a government-issued ID and proof of address. These documents help verify your identity and protect against fraudulent activity.
Wait for approval: The verification process may take some time. You will be notified via email once your KYC is approved.
More detailed instructions:
For enhanced security, you need to enable Two-Factor Authentication (2FA). Follow these steps:
Navigate to Security settings: Go to your account settings and locate the Two-Factor Authentication (2FA) section.
Enable 2FA: Follow the instructions to enable 2FA, typically involving scanning a QR code with an authenticator app (such as Google Authenticator) and entering the generated code.
After registering, completing KYC verification, and enabling 2FA, you can generate an API key:
Navigate to API settings: Go to your account settings and locate the API settings section.
Generate new API Key: Click the "Generate API Key" button. Your new API key will be displayed. Copy this key and store it securely. You will need it to authenticate your API requests.
Authentication is done by sending the following HTTP headers:
apiKey: Your public API key (pass through the request's header "x-api-key")
apiSecret: Your API secret key (use to hash query)
api-signature: A signature of the request you are making. It is calculated as hex(HMAC_SHA256(apiSecret, queryString). See the example calculations below.
Hint: queryString is make from your query params (it doesn't need query data) and the timestamp you execute the request.
Example
More detailed instructions: