Help: Cannot applicationAccessKey in Workflows HTTP Headers

AppSheet AppSheet Q&A
1

Hi there!

I’m trying to create a workflow that adds a row to a table based on adds/updates from another table.

I’ve been following this guide: https://help.appsheet.com/en/articles/1979979-invoking-the-api

But I currently have an issue with adding the HTTP Header, every time I click on save it removes itself therefore giving me a 400 error code when I test it.

3X_9_e_9ede5ba3369464ca920dedc2c888c91fdaa8b8fd.png
3X_9_e_9ede5ba3369464ca920dedc2c888c91fdaa8b8fd.png890×130 8.05 KB

I’m wondering if this is an issue on my end? Here’s the data i’m using.

URL: https://api.appsheet.com/api/v2/apps/myAppID/tables/Remarks/Action

JSON: {
“Action”: “Add”,
“Properties”: {
“Locale”: “en-US”,
“Location”: “47.623098, -122.330184”,
“Timezone”: “Pacific Standard Time”,
“RunAsUserEmail”: “zbcosico@globe.com.ph”
},
“Rows”: [
{
“_RowNumber” : “<<UNIQUEID()>>”,
“PRODUCT” : “<<[PRODUCT]>>”,
“ACCOUNT NUMBER (GLOBE)” : “<<[ACCOUNT NUMBER (GLOBE)]>>”,
“ICCBS CIRCUIT ID”: “<<[ICCBS CIRCUIT ID]>>”,
“ACCOUNT NUMBER (CSP) / BILLING ID” : “123”,
“Company Name” : “<<[Company Name]>>”,
“Customer Name” : “<<[Customer Name]>>”,
“Activation Date” : “<<[Activation Date]>>”,
“Status” :“<<[Remarks]>>”,
“Remarks” : “<<[Remarks]>>”
}
]
}

HTTP Header: applicationAccessKey: “V2-GaKAa-im7nw-kmNpE-THoQL-tMzmR-ErQHh-8Ayf2-tqS1M”

2

I am not familiar with this functionality BUT there was an announcement a few days ago about application access keys. Maybe it will help you?

[Invoking the REST API from a Webhook](https://community.appsheet.com/t/invoking-the-rest-api-from-a-webhook/32837) Announcements

We have made an improvement to workflow webhooks that invoke the REST API. Previously, when a workflow webhook invoked the REST API, the Editor automatically added an HTTP header that contained the Application Access Key. We have now made this easier and more automatic. When a webhook is invoked, we now check whether the webhook is invoking the REST API. If so, we now automatically add the Application Access Key just before invoking the webhook POST call. There is no longer any need for you to…

1 Like
3

I have updated the article to try to make it clearer.
See https://help.appsheet.com/en/articles/1979979-invoking-the-api

2 Likes
4

Hello, from my understanding you don’t have to specify the Application Access Key in the HTTP header when invoking the API. But it still gives me a 400 error, i’m pretty sure that my URL is correct and I’ve even set my JSON rows to be static variables with the appropriate data type, any idea why this is still the case?

3X_6_f_6f5f7aacbecc5b1eefa949577dd5daea9a7ab84c.png
3X_6_f_6f5f7aacbecc5b1eefa949577dd5daea9a7ab84c.png892×288 20.7 KB

5

Any chance your Application Access key is expired? Please check that from Manage > Integrations

1 Like
6

Hi thank you for the reply!!

I did hope that was the case, I used a new access key because the default one is deprecated, I even made a new one just now to test but unfortunately I still get a 400 error

7

Would you please email support@appsheet.com with details like
#1 - Account ID number
#2 - App name
#3 - Workflow rule name
#4 - Would you please give access to your app/account, so we can investigate what the issue might be. You can do that from www.appsheet.com > My Account > Settings > “Allow AppSheet staff to access…”.

1 Like