Yes, thanks, I realised that after my original post, hence the edit
referring to, what seems to be, a non-editable Post Body Template. Based
on the other posts available, it seems that there is no option to change
this template structure. I know that I could send the request to my own
endpoint, re-format it, and then send it on to the API I'm dealing with
but I'm just surprised that there's no option to change the structure
within the workflow action.
I have a use case where we want to send data to a 3rd party endpoint as
part of a workflow, however, it seems like this isn't currently
possible. I'm aware of the External API action within workflows but it
looks like this is limited to GET requests rather than POST. Has anyone
found a solution for this use case?Edit to original question: it
actually looks like it's the request structure that's the problem. The
API endpoint I'm calling is expecting a flat JSON structure, whereas the
Post Body Te...
Feel like I must be missing something obvious but I couldn't see any
help documentation that explains the process of moving a build from
stage to production. I have run aio app deploy and everything is working
nicely in Stage but I couldn't see a way to move things across. I can
see it's possible for me to add the Services etc again in the Production
environment but is that meant to be the process?
These are the debug statements I'm seeing:I'm using Postman to make a
request to the same endpoint with the same 4 headers (authorization,
content-type, x-gw-ims-org-id and x-api-key) and header values, not
seeing any issues.
I've created a project with the intention of using the Privacy Service
APIs. So i've made a few small tweaks:1) Changed the endpoint to
Changed requiredHeaders to include ['Authorization', 'x-api-key',
'x-gw-ims-org-id']I've tried the request in Postman and it works fine,
so I know there isn't an issue with the headers, but when I run it in
localhost I get a 500 error: Am I missing something obvious?Edit: I