REST with POST method reading AppSheet Database

Hi @mnoordam 

I set up my own app in Appsheets to see if I got the same issues.

Here is the file I generated.

<api:script xmlns:api="http://apiscript.com/ns?v1" xmlns:xs="http://www.w3.org/2001/XMLSchema">

  <!-- See Column Definitions to specify column behavior and use XPaths to extract column values from JSON. -->
  <api:info title="response" desc="Generated schema file." xmlns:other="http://apiscript.com/ns?v1">
    <!-- You can modify the name, type, and column size here. -->
    <attr name="_RowNumber"            xs:type="string"   readonly="false"              other:xPath="/json/_RowNumber"            />
    <attr name="Category"              xs:type="string"   readonly="false"              other:xPath="/json/Category"              />
    <attr name="ID"                    xs:type="string"   readonly="false"              other:xPath="/json/ID"                    />
    <attr name="Last_Edited"           xs:type="datetime" readonly="false"              other:xPath="/json/Last Edited"           />
    <attr name="Last_Edited_By"        xs:type="string"   readonly="false"              other:xPath="/json/Last Edited By"        />
    <attr name="Name"                  xs:type="string"   readonly="false"              other:xPath="/json/Name"                  />
    <attr name="Picture"               xs:type="string"   readonly="false"              other:xPath="/json/Picture"               />
    <attr name="Related_List_Contents" xs:type="string"   readonly="false"              other:xPath="/json/Related List Contents" />
  </api:info>

  <api:set attr="DataModel" value="DOCUMENT" />
  <api:set attr="URI"value="https://api.appsheet.com/api/v2/apps/bee87e8e-6af5-4bec-a598-92efe436868d/tables/Items/Action?ApplicationAccessKey=V2-7vA2m-wx869-5d3fo-Nzy1s-dp6Ny-1234-56789-abcd" />

  <api:set attr="JSONPath" value="$." />

  <!-- The GET method corresponds to SELECT. Here you can override the default processing of the SELECT statement. The results of processing are pushed to the schema's output. See SELECT Execution for more information. -->
  <api:script method="GET">
    <api:set attr="method" value="POST"/>
	<api:set attr="contenttype" value="application/json"/>
	<api:set attr="data">{"Action": "Find","Properties": {"Locale": "en-US"}}</api:set>
    <api:call op="jsonproviderGet">
      <api:push/>
    </api:call>
  </api:script>

</api:script>

It works for me. The only difference is that I have the ApplicationAccessKey set as an URL parameter instead of an header.

UPDATE

It works for me no matter if I have set up the header in my data source or added it. I think it is something else, but it is not about it not being able to do post calls.

This is my log

I did exactly the same. Postman works like a charm, 

postman Results → TX → generated new RSD → Edit URI

You do use the REST 2023 driver?

I try to always use the newest available version the newest one currently is 23.0.8565.0

I tried both the REST one and the JSON one and they both behaved the same way.

If you connect with the Response.json file it works with no issues right?

I will try yours.

Hi @mnoordam 

I have made a file where the header is directly applied in the setup. This works for me.

Let me know if it works for you as well.

You can’t upload RSD files to this, so I have added an extra .txt to the file, remember to remove this before it can be used.

….

HOLDUP. It works!
I did a reset + supplied the URI again.

But you meant deleting the whole URI. That was it. So simple. :-|

Thx for yoru assistance!!