> For the complete documentation index, see [llms.txt](https://docs.emobiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emobiq.com/emobiq-server/002-api/004-method.md).

# Method

## Description

Each Action can hold five different Methods, and each Method can have different behavior among each other, and can be configured independently.

![](/files/RFgfUCpNTPYQ3CVThFF7)

## Supported Methods

* **GET**:
  * Description: Used to respond with data requested by the client without making any changes to the server's state.
  * Example use cases:
    * Retrieving data from a database: Fetching user information or product details to send back to the client.
* **PATCH**:
  * Description: Used to apply partial modifications to a resource on the server.
  * Example use cases:
    * Updating user preferences: Applying changes to specific settings within a user's profile without affecting the entire profile.
    * Editing content: Modifying specific fields of an article or post without altering the rest of the content.
* **PUT**:
  * Description: Used to either update an existing resource or create a new resource with a specific identifier.
  * Example use cases:
    * Updating existing records: Replacing an outdated version of a product description with a new one in the database.
    * Creating resources with specific IDs: Using a PUT request to create a new entry in a catalog with a designated product code.
* **POST**:
  * Description: Used to handle data submitted by the client and take appropriate actions based on that data.
  * Example use cases:
    * Processing form submissions: Receiving user inputs like login credentials or feedback and validating them on the server.
    * Creating new records: Accepting data for generating new posts, comments, or user profiles and storing them in the database.
* **DELETE**:
  * Description: Used to initiate the removal of a resource from the server.
  * Example use cases:
    * Deleting content: Handling requests to remove outdated articles or media files from the server's storage.
    * Deactivating accounts: Processing requests to delete user accounts and associated data, making them no longer accessible.

## Note

While strict adherence to the above HTTP methods is not mandatory, it is recommended to follow the standard guidelines when building your API.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.emobiq.com/emobiq-server/002-api/004-method.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.