Errors

rail_not_available

That plan does not use this rail

From the Volume plan upwards, Njiwa sends only over Meta's Business Cloud API. A number cannot be linked by scanning a code on those plans.

What to do

Add the number as a Cloud rail number instead. At those volumes a number that gets restricted takes a whole business off the air, and the Cloud API is the rail with an agreement behind it - which is why this is refused rather than warned about.

The shape

{
  "error": {
    "type": "...",
    "code": "rail_not_available",
    "message": "...",
    "docs": "https://docs.njiwa.upeo.ai/errors/rail_not_available"
  }
}