[Solved] how can I fix a 403 error using the WEB API

Questions about Thunkable Web API's
1

Hello everyone :grinning:
I am working on a geolocation app which uses this api .
And when I run it I get a 403 error which is listed as no HTTPS access in the documentation. Even though my web url starts with HTTP .
And it works fine in the browser as expected.
Is this a thunkable issue? or I have to make changes in my blocks?
these are my blocks :-

image
image829×628 49.7 KB

image
image386×722 14 KB

Thanks in advance.

1 Like
2

What is the value of the green error block? It looks like you’re displaying the green status block but we’d need to know what error you’re getting.

3

It does not give any error as when I put the green error block under if-condition the condition does not take place rather gives the status.

4

Have you tried set Label11’s Text to [error] in the then do section (not inside the if block)? When you do that, is there a value or is it blank?

5

by doing that I get the label as undefined…

6

Have you tried it in the companion app? Perhaps is a CORS issue?

7

Even if your URL starts with HTTP, the Web API will force it to HTTPS. This is I think by design of the Web API component.

1 Like
8

Is there a way to bypass the issue?

1 Like
9

See this post

10

What are browser developer tools?

11

image
image1292×704 122 KB

2 Likes
12

I tried the test in my iPhone and it works great. but while live testing it in a pc the status is 403. Anyways
solved… thanks @tatiang @muneer :grinning:

2 Likes
13

That is great. It means that the developers of Thunkable have solved the earlier reported issue even if it wasn’t a complete solution as you have experienced.

Happy Thunking!

3 Likes