What error are you getting?
And the brackets allow for a dynamic parameter.
Try setting “pretty=false” I believe Bubble uses raw.
Ok.
Here’s the current URL I’m using: https://api.everyoneapi.com/v1/phone/[number]?data=name,address&pretty=false
Same error.
If I emailed EveryoneAPI support, what would I want to ask them?
Try the call on Postman before emailing them. Postman should give you a more specific error. Check errors on the Everyone API doc.
Ok. I will. Thanks for the help troubleshooting this.
Huh. So I’m getting a 401
401 UNAUTHORIZED - If you incorrectly specify your account credentials, you will receive a 401 UNAUTHORIZED response. This means you need to check that you have the correct Account SID and Auth Token specified.
But my login details are correct: https://api.everyoneapi.com/v1/phone/+15162536232?data=name,address&account_sid=ACc7354c9b65a646fd92a362800929e4a4&auth_token=AU705e499560fc4f1b8f1166d8a0cf57da&pretty=true
Heres my account details:
Perhaps I’m sending the login details in the wrong way?
Should I just email support and ask them what I should be sending?
Try using an authorization header instead of HTTP Basic
Follow this on the documentation using the base64 encoding
Ok, I’m unclear how to do this. Do you I need to pick another option here?
Or do I still use “basic authentication” and then write the SID and Token differently?
I contacted Telo support. He said he wasn’t getting an error when putting it into the browser.
(https://api.everyoneapi.com/v1/phone/+15162536232?data=name,address&account_sid=ACc7354c9b65a646fd92a362800929e4a4&auth_token=AU705e499560fc4f1b8f1166d8a0cf57da&pretty=true) it will return text.
I thought maybe the issue was that it was returning text and bubble needs json.
I then added “&format=json” and it still didn’t work.
If I can get it working in postman but not bubble, perhaps need to connect Telo and bubble support?
Bubble support doesn’t support APIs right now as they have bigger priorities unless it is a blatant bug in the API connector. Make sure you try ever possible authentication and header you can think of before connecting them.
Ok thanks. I’ll see if Telo support can help out then!
Good news. I figured it out! I changed the authentication settings in Bubble from “HTTP Basic Auth” to “private key in the URL” and it worked.
Any idea why this would work?
1 Like
Some APIs may have used a different method of HTTP Basic Auth that is now depreciated, header authorization is always much easier to connect in my opinion.
Okay. Is header auth when the SID and TOKEN is in the URL?