POST
/
v1
/
terminals
/
unassign
/
{accountId}
curl --request POST \
  --url https://api.nomba.com/v1/terminals/unassign/{accountId} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'accountId: <accountid>' \
  --data '{
  "serialNumber": "55555555",
  "terminalLabel": "Testing"
}'
{
  "code": "00",
  "description": "Success",
  "data": {
    "terminalId": "201124LM",
    "serialNumber": "55555555",
    "accountId": "01a10aeb-d989-460a-bbde-9842f2b4320f",
    "parentAccountId": "<string>",
    "merchantName": "trident and rees",
    "terminalLabel": "Testing",
    "createdAt": "2020-09-23T10:21:48.789Z",
    "updatedAt": "2023-09-04T15:23:55.173Z"
  }
}

Authorizations

Authorization
string
headerrequired

Nomba authenticates API calls with OAuth2 HTTP bearer tokens. There are two methods of authentication; Client-Credentials method and PKCE (Proof Key for Code Exchange) method. In each of the methods, You will get an ACCESS_TOKEN. You need to use an "Authorization" HTTP header to provide your ACCESS_TOKEN. For example: Authorization: {ACCESS_TOKEN}.

Headers

accountId
string
required

The parent accountId of the business.

Path Parameters

accountId
string
required

The accountId whose terminals are to be fetched.

Body

application/json
serialNumber
string
required

Serial number

terminalLabel
string

Terminal label

Response

200 - application/json
code
string
required

Response Code

description
string
required

Response description

data
object
required