What guides your choice of HTTP method (GET, POST, PUT, etc.) for an API?

The choice of HTTP method for an API depends on the semantics of the operation and REST standards:

• GET — for retrieving data without changing the server state. Idempotent and safe.
• POST — for creating new resources or performing operations that change state. Not idempotent.
• PUT — for replacing or creating a resource at a known URI. Idempotent.
• PATCH — for partial updates to a resource.
• DELETE — for deleting a resource. Idempotent.

Guided by REST principles and the expected behavior of the client and server. For example, to get a list of users — GET /users. To create a new user — POST /users. To update a specific user — PUT /users/{id}.

This approach ensures predictability and API compatibility.