Device Reachability Status API

Overview

The Device Reachability Status API indicates whether a device is currently reachable on the mobile network.

• Version: 1.0.0
• Base URL: https://api.pxg.konera.com/camara
• Path: /device-reachability-status/v1/retrieve
• OpenAPI: device-reachability.json

Typical use cases

• Pre‑call checks – Determine if a device is likely reachable before initiating important calls.
• Notification reliability – Decide whether to fall back to alternative channels when SMS/push may not reach the device.
• Fraud checks – Flag risky flows when a device is consistently unreachable.

Security

• OAuth2 Client Credentials
  • Token URL: https://auth.konera.com/oauth2/token
  • Scope: device-reachability.read – Read device reachability signal

Headers

• x-correlation-id (optional, string) – Correlation ID for request tracing.

Request

POST https://api.pxg.konera.com/camara/device-reachability-status/v1/retrieve

Body schema: DeviceReachabilityRequest

{
  "phoneNumber": "+14155550123",
  "maxAgeSeconds": 60
}

• phoneNumber (string, required) – MSISDN in E.164 format.
• maxAgeSeconds (integer, optional) – Maximum acceptable age of the reachability information, in seconds.

Responses

200 – Reachability status returned

Body schema: DeviceReachabilityResponse

{
  "isReachable": true,
  "assessedAt": "2026-02-10T10:00:00Z"
}

• isReachable (boolean) – Indicates whether the device is reachable.
• assessedAt (string, date-time) – Time when reachability was assessed.

HTTP status codes

Standard Error schema with:

• 200 OK – Reachability successfully assessed.
• 400 Bad Request – Invalid phone number or parameters.
• 401 Unauthorized – Invalid/missing token.
• 403 Forbidden – Caller not permitted to query reachability.
• 429 Too Many Requests – Rate limit exceeded.
• 500 Internal Server Error – Unexpected server error.