Caller ID names often arrive in all caps. A familiar company name can look a little wrong in JSON, but that is how the record is supplied.
GET /caller/+18004633339
{
"phone": "+18004633339",
"valid": true,
"country": "US",
"caller": "FEDEX"
}
We keep that casing in /caller. Automatically turning FEDEX into Fedex would be a guess at how the name should be written. Personal names are harder still. There is no reliable way to recover someone's preferred spelling from an all-caps record.
These records are called CNAM, short for caller name. They can also contain abbreviations, shortened names, or generic labels. The field gives you the record available for caller ID, with its original wording.
An empty record still counts as a lookup
The service covers numbers in the North American Numbering Plan, the countries and territories sharing the +1 calling code. A valid number outside that area returns caller: null without using a caller ID lookup.
A covered number can return null too, when no name is available. That result uses one lookup from your allowance because the check completed. If the caller-name check gets no answer, the API returns HTTP 200 with caller: null and releases the reserved lookup without billing it.
The Free plan includes 100 caller ID lookups a month. Paid plans have their own allowances and additional-usage rates, listed on the caller ID page.