ส่งค่าที่อ่านได้จากเซนเซอร์ด้วย POST

GET pulls data in. To push your sensor readings up to a server, you use a POST request instead. 📤

A GET asks for data, while a POST sends a body of data to the server to create or store something new.

You still create an HTTPClient and call begin() with the endpoint URL. Only the sending step changes for a POST.

Decide what to send. A small JSON string holding your readings is a clean, standard way to package the data.

Set a Content-Type header so the server knows your body is JSON. Without it, the server may misread your data.

Call POST() and pass your body. It returns a status code just like GET did, so you can confirm it worked.

A 200 or 201 means the server accepted your data. 201 specifically means a new record was created.

Servers often reply to a POST too, maybe an id or a confirmation. Read it with getString() if you need it.

As always, call end() after a POST to release the connection and keep your board healthy for the next send.

You rarely POST every loop. Read a sensor, then upload once every few seconds or minutes to save power and bandwidth.

The server expects fields in a specific format. If your JSON keys or types are wrong, it will reject the reading.

You are sending a JSON body to your backend. Which request method fits?

You packaged readings as JSON, set the Content-Type header, sent them with POST(), checked the code, and closed up. Your data is in the cloud. 🎉