Integrations: Passing parameters in the body of a HTTP POST request

It's difficult to know what the issue is without knowing what the source system looks like/expects.

I assume your body is formatted something like the following:

a!toJson(
{
"createTransactionRequest": {
"merchantAuthentication": {
"name": cons!AUTHORIZE_DOT_NET_API_LOGIN_ID,
"transactionKey": cons!AUTHORIZE_DOT_NET_TRANSACTION_KEY
},
"transactionRequest": {
"transactionType": "authCaptureTransaction",
"amount": "100.00",
"payment": {
"creditCard": {
"cardNumber": "5424000000000015",
"expirationDate": "1220",
"cardCode": "999"
}
}
}
}
}
)

Referenced from the Integration Tutorial: docs.appian.com/.../Integration_Tutorial.html

The above tutorial shows Appian working with a POST request passing parameters within the body (tested working for both querying and modifying data). However, it seems as though there is some configuration issue/mismatch from the API as Appian cannot retrieve the data in a similar manner as seen in the above example.

I will outline some things to double check along with alternatives, hopefully they are helpful.

When using a POST request to retrieve data with an Integration be sure to pay attention to the Usage value. The Usage value should be set to the "Queries data" option. When selecting POST for the Method value Appian automatically sets the Usage value to "Modifies data."

The only other option I see is implementing a GET version of the request both in Appian and for the API.

It's difficult to know what the issue is without knowing what the source system looks like/expects.

I assume your body is formatted something like the following:

a!toJson(
{
"createTransactionRequest": {
"merchantAuthentication": {
"name": cons!AUTHORIZE_DOT_NET_API_LOGIN_ID,
"transactionKey": cons!AUTHORIZE_DOT_NET_TRANSACTION_KEY
},
"transactionRequest": {
"transactionType": "authCaptureTransaction",
"amount": "100.00",
"payment": {
"creditCard": {
"cardNumber": "5424000000000015",
"expirationDate": "1220",
"cardCode": "999"
}
}
}
}
}
)

Referenced from the Integration Tutorial: docs.appian.com/.../Integration_Tutorial.html

The above tutorial shows Appian working with a POST request passing parameters within the body (tested working for both querying and modifying data). However, it seems as though there is some configuration issue/mismatch from the API as Appian cannot retrieve the data in a similar manner as seen in the above example.

I will outline some things to double check along with alternatives, hopefully they are helpful.

When using a POST request to retrieve data with an Integration be sure to pay attention to the Usage value. The Usage value should be set to the "Queries data" option. When selecting POST for the Method value Appian automatically sets the Usage value to "Modifies data."

The only other option I see is implementing a GET version of the request both in Appian and for the API.

Thanks for taking the time to respond.

The Usage value is set to 'Queries Data'.

The Content Type of the body is set to Multipart Form Data.

This particular Web API does not work when the parameters are passed as 'Parameters' (in Appian or Postman), only when they are passed in the request body (which works with Postman). The API is only provided as a POST method. I will try to get more details about the 'expectations' of the API from the service provider.