We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm attempting to retrieve the caller-name and carrier types from a NumberLookup but those properties are always returned as null.
caller-name
carrier
null
I'm using the following code:
\Telnyx\NumberLookup::Retrieve($number, ["type" => ["caller-name", "carrier"]]);
but it appears that ?type=carrier&type=caller-name isn't appended to the request URL.
?type=carrier&type=caller-name
Is there a fix for this or do I need to just use cURL?
The text was updated successfully, but these errors were encountered:
I can't remember if the library will implode arrays. The lib might be ignoring that param.
Before you switch to cURL, try just using a string instead of an array.
\Telnyx\NumberLookup::Retrieve($number, ["type" => "caller-name,carrier"]);
Sorry, something went wrong.
Sorry I just realized this endpoint needs two type parameters. This is how I have it setup in my test code from several years back:
\Telnyx\NumberLookup::Retrieve($number, ["type" => "caller-name", "type" => "carrier"]);
You're suggesting using a duplicate array key?
In any case, that code doesn't work in v2.9.0 nor 3.0.0.
The caller_name property is still null even when only using the following:
caller_name
\Telnyx\NumberLookup::Retrieve($number, ["type" => "caller-name"]);
No branches or pull requests
I'm attempting to retrieve the
caller-name
andcarrier
types from a NumberLookup but those properties are always returned asnull
.I'm using the following code:
but it appears that
?type=carrier&type=caller-name
isn't appended to the request URL.Is there a fix for this or do I need to just use cURL?
The text was updated successfully, but these errors were encountered: