Generate Token
POST/Login/Customer/Api/Verify
Authenticates an API customer with email and password and returns a bearer access token that must be sent on every subsequent request.
How it works
- Call this endpoint once with your API customer credentials.
- Persist the returned token securely on your side.
- Send the token in the
Authorizationheader of every other request:Authorization: Bearer {token}. - When the token expires, call this endpoint again to obtain a new one.
The optional callbackData field is echoed back unchanged in the response and is
useful for correlating the login attempt with a record on your side.
Sample request
POST /Login/Customer/Api/Verify HTTP/1.1
Host: api.hyperteknoloji.com
h-region-code: TR
Content-Type: application/json
{
"Password": "your-password",
"callbackData": "optional-correlation-id"
}
Sample response
{
"data": {
"Token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
"Expiration": "2026-05-14T10:30:00Z",
"callbackData": "optional-correlation-id"
},
"success": true,
"message": "OK"
}
Notes
- This endpoint is anonymous; do not send an existing
Authorizationheader. - The credentials must belong to a customer flagged as an API customer (
IsAPI = 1). - The
h-region-codeheader defaults toTRwhen omitted.
Request
Responses
- 200
- 400
Token generated successfully.
Invalid credentials or invalid request payload.