[SOLVED] Payload not passed anymore

Hi, before the recent update of appwrite cloud to 1.4.3, I was calling a function remotely with my data payload as a json string using curl.

Now apparently I'm not getting data anymore inside my function, did something change?

TL;DR

The user was experiencing an issue where their payload was not being passed anymore after an update to the Appwrite cloud. They initially asked if anyone had any insight or solutions to their problem. Some users suggested using the new domain and specifying the method and content type header. Another user mentioned that the parameter for the payload has changed from "data" to "body." The user eventually solved their issue by changing the URL to the new domain and updating their function. Solution: Update the URL to the new domain and change the parameter for the payload from "data" to "body."

Payload now doesn't exist

But body

How to pass it using curl?

To pass data in the body using curl, you can use the -d or --data option followed by the data you want to send. For JSON data, you would also typically set the Content-Type header to application/json. Here's an example:

TypeScript

curl -X POST "http://your-appwrite-function-endpoint" \
     -H "Content-Type: application/json" \
     -d '{"key1": "value1", "key2": "value2"}'

Replace http://your-appwrite-function-endpoint with your actual function endpoint and modify the JSON data as needed. This will send the data in the body of the request.

@D5 is there any other way of passing it through body?

I see. So maybe my issue is that req.payload has changed, when retrieving data?

I'm logging req, but body is always empty "", after the update

Can you show your log and your code once

I solved changing the url to the new domain one and updated the function too, no idea why though

So now I'm using req.body

as D5 mentioned, the param is no longer data It has changed to body

See 1.4 docs vs 1.3 docs

Yeah I solved changing that but it wasn't enough, because for some reason I didn't receive the body anyway. After upgrading both the function and the caller (to use the new domain thing and to pass the body json directly) it worked though, thanks to you all

it should have worked if you changed the param in the body client...or maybe you needed to specify the method and content type header as well..

Hmm no and this function I had was working because I used it until yesterday. No idea why though, maybe you can't pass the body without using the new domain thing?