# Are Thunkable and WalMart API compatible?

**URL:** <https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092>\
**Category:** Questions about Thunkable X\
**Tags:** webapi\
**Created:** [August 8, 2022, 6:58pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092 "2022-08-08T18:58:42Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryan\_hall\_apps](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@ryan\_hall\_apps](https://community.thunkable.com/u/ryan_hall_apps)\
**Post date:** [August 8, 2022, 6:58pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/1 "2022-08-08T18:58:42Z")

</div>

I am trying to connect my thunkable app to WalMart web API.

I am reading the docs to connect it and it is saying that HTTP requests will fail.

From Documnets:

> All API requests must be made over [HTTPS](http://en.wikipedia.org/wiki/HTTP_Secure). Calls made over plain `HTTP` will fail. API requests with an incorrect authentication will also fail and will return a Status Code of `401` .

[Link to Docs](https://integrations.impact.com/impact-publisher/reference/authentication).

I have tried setting up my headers a thousand different ways. Am I entering something wrong or will the platforms not work together?

I have my headers set up as follows:

```
 Accept: application/json
 Authorization: Basic <SSID>:<Auth Token>

```

---

<div class="post-metadata">

**Author:** ![jared](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/jared/32/138473_2.png) [@jared](https://community.thunkable.com/u/jared)\
**Post date:** [August 8, 2022, 7:14pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/2 "2022-08-08T19:14:24Z")

</div>

Did you test from a device or the online builder ?

---

<div class="post-metadata">

**Author:** ![ryan\_hall\_apps](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@ryan\_hall\_apps](https://community.thunkable.com/u/ryan_hall_apps)\
**Post date:** [August 8, 2022, 7:34pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/3 "2022-08-08T19:34:48Z")

</div>

Online gives me a fetch error.

Testing on the live view gives me an “unauthorized” error.

---

<div class="post-metadata">

**Author:** ![zander](https://avatars.discourse-cdn.com/v4/letter/z/ecb155/32.png) [@zander](https://community.thunkable.com/u/zander)\
**Post date:** [August 8, 2022, 8:47pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/4 "2022-08-08T20:47:50Z")

</div>

Have you been able to get it to work using something like postman? If not i would start there first.

---

<div class="post-metadata">

**Author:** ![ryan\_hall\_apps](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@ryan\_hall\_apps](https://community.thunkable.com/u/ryan_hall_apps)\
**Post date:** [August 8, 2022, 10:01pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/5 "2022-08-08T22:01:57Z")

</div>

I have never heard of Postman but it is handy. Thank you @zander.

Result from postman cURL call:

```auto
    "Status": "ERROR",
    "Message": "Bad credentials"
     Status: 401 unauthorized

```

From API documents:

> All API requests must be made over HTTPS. Calls made over plain `HTTP` will fail. API requests with an incorrect authentication will also fail and will return a Status Code of `401` .

Looks like it does not work since postman is also sending a HTTP call. Does anyone know if there is a way to send a HTTPS cURL call from Thunkable?

---

<div class="post-metadata">

**Author:** ![zander](https://avatars.discourse-cdn.com/v4/letter/z/ecb155/32.png) [@zander](https://community.thunkable.com/u/zander)\
**Post date:** [August 8, 2022, 10:27pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/6 "2022-08-08T22:27:44Z")

</div>

So I don’t think its the https issue. I re read the socuments and it looks like its a credentials issue.

`API requests with an incorrect authentication will also fail and will return a Status Code of 401`

However I found this link that kind of teaches you how to do a https call

> **[Postman - POST Requests](https://www.tutorialspoint.com/postman/postman_post_requests.htm#)**
>
> Postman - POST Requests, Postman POST request allows appending data to the endpoint. This is a method used to add information within the request body in the server. It is commonly used

---

<div class="post-metadata">

**Author:** ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)\
**Post date:** [August 8, 2022, 11:41pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/7 "2022-08-08T23:41:18Z")

</div>

You need a conversation tool for your authentication credentials.

You can use `Postman` if you want. Give it the `SSID` and `Auth Token` and `Postman` would give you an encrypted string which you will need to use in the `authorization` entry of your `header`.

---

<div class="post-metadata">

**Author:** ![ryan\_hall\_apps](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@ryan\_hall\_apps](https://community.thunkable.com/u/ryan_hall_apps)\
**Post date:** [August 9, 2022, 12:30am UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/8 "2022-08-09T00:30:59Z")

</div>

I gave poatman Basic Auth tool information. I entered my ssid and auth token. I got the same result in postman as I did in thunkabke.

Status 401.

Am I missing something?

---

<div class="post-metadata">

**Author:** ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)\
**Post date:** [August 9, 2022, 2:37am UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/9 "2022-08-09T02:37:18Z")

</div>

You can easily test if you are missing something or not.

The API is using **Basic** authentication which means you can run it directly from your browser.

In your browser (Chrome or Firefox or any other) start a new tab and in the browser URL type:

SSID:Auth-code@[http://your-api-end-point](http://your-api-end-point)

So, if your SSID is ryan and your auth code is abcd1234 and your API is [http://walmart-api](http://walmart-api) then your URL should be

ryan:abcd1234@[http://walmart-api](http://walmart-api)

This should work directly from the browser.

---

<div class="post-metadata">

**Author:** ![ryan\_hall\_apps](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@ryan\_hall\_apps](https://community.thunkable.com/u/ryan_hall_apps)\
**Post date:** [August 9, 2022, 9:16pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/10 "2022-08-09T21:16:48Z")

</div>

@muneer & @zander

Thank you for sticking with me on this and letting me know I’m most likely wrong in how I was inputting data.

I used Postman for the HTTP diagnosis. On the left side of Postman there is a \</\> symbol that shares the cURL code. I noticed that the Authorization header was changed from how I was entering it in Thunkable.  
I was entering my property as: “Authorization” with value: “Basic SSID:auth-code”. However when I looked at the code in postman it changed it to a long key.

I have no idea how to make this key or where is came from. I’m sure it has something to do with Basic Auth protocols? So to solve it I put my property as: “Authorization” with value: “Basic long-random-key”.

Anyways it is solved thanks to this. I appreciate everyone who helped. Stay tuned for more questions. 🤣

---

<div class="post-metadata">

**Author:** ![zander](https://avatars.discourse-cdn.com/v4/letter/z/ecb155/32.png) [@zander](https://community.thunkable.com/u/zander)\
**Post date:** [August 9, 2022, 9:39pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/11 "2022-08-09T21:39:17Z")

</div>

> [@muneer](#):
>
> You can use `Postman` if you want. Give it the `SSID` and `Auth Token` and `Postman` would give you an encrypted string which you will need to use in the `authorization` entry of your `header`.

This is where that long string came from.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/thunkable/original/3X/0/f/0f59f292712368bce16ff80133ae10de8a6f27e8.png) [@system](https://community.thunkable.com/u/system)\
**Post date:** [November 7, 2022, 9:39pm UTC](https://community.thunkable.com/t/are-thunkable-and-walmart-api-compatible/1992092/12 "2022-11-07T21:39:51Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
