API reference
GET
/applicationIdentify your application
Identify the authenticated application and environment
Overview
Check which account, application and environment a secret belongs to. Application names are for display; the server derives stable identity from the key.
Renaming a key changes its current display name but preserves its application ID. You do not need to send the name in a payment request.
Example request
curl https://api.nuepay.net/v1/application \
-H "Authorization: Bearer $NUEPAY_TEST_KEY"Example response
{
"data": {
"application_id": "00000000-0000-4000-8000-000000000001",
"application_name": "Online store",
"account_number": "YOUR_ACCOUNT_NUMBER",
"mode": "test",
"livemode": false
}
}Examples omit timestamps for readability. Use POST /quotes to confirm current fees rather than hard-coding these examples.
Response fields
| Field | Type | Details |
|---|---|---|
application_id | string | See the response and related guide. |
application_name | string | See the response and related guide. |
account_number | string | See the response and related guide. |
mode | string | live, test |
livemode | boolean | See the response and related guide. |
HTTP status codes
| Status | Meaning |
|---|---|
200 | application_id, application_name, account_number, mode, livemode. |
201 | Invalid credentials. |
202 | Access unavailable or operation paused. |
203 | Resource not found in this application and environment. |
204 | Idempotency conflict, insufficient funds, or payout setup required. |
205 | Invalid input; inspect errors and code. |
206 | Rate limit exceeded. |
207 | Live provider unavailable; accepted payments can still be read or retried. |
Errors contain a stable code and support request_id. See error handling for recovery guidance.