> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/tasks/tasks/odoo/request.md). # Request Task version: 1.0.0 Required Frends version: 5.5+ Required .NET version: 6.0 Compatible Agents: Crossplatform Source code: ## Task Parameters {% tabs %} {% tab title="Input" %} | Name | Description | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Model : `String` |

Model to call in the request. You can get a list of Odoo model by calling the "ir.model" model

with the "search\_read" method and the fields "name", "model" and "state".


Default: res.partner
Example: res.partner

| | Method : `String` |

Method to execute in the request.


Default: search\_read
Example: res.partner

| | Args : `String` |

Method arguments as JSON.


Default: \[]
Example: \[ "arg1", 1 ]

| | Kwargs : `String` |

Method keyword arguments as JSON.


Default: {}
Example: { "key1": "value1", "key2": "value2" }

| | {% endtab %} | | {% tab title="Options" %} | Name | Description | | ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | OdooUrl : `String` |

Odoo URL.


Default:
Example:

| | Username : `String` |

Username to authenticate with.


Default:
Example:

| | 🗝Password : `String` |

Password to authenticate with.


Default: -
Example: Password!

| | Database : `String` |

Odoo database.


Default: MyDatabase
Example: MyDatabase

| | ThrowExceptionOnErrorResponse : `Boolean` |

If true, the task throws an exception if the response from Odoo contains an error.

If false, the task returns the error message in the result.


Default: False
Example: Example of the parameter value

| | {% endtab %} | | | {% endtabs %} | | ## Task Result | Name | Description | | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Success : `Boolean` |

True if the operation was successful. False if the operation failed. If optional parameter ThrowExceptionOnErrorResponse is set to true, the task throws an exception if the response from Odoo contains an error.
Example: true

| | Error : `String` |

Error message if the operation failed.
Example: Error message

| | Data : `Object` |

Data returned by the operation in JToken format. You can use dot notation to access the field values.
Example: \[ { "field1": "value1" }, { "field1": "value2" } ]

| ## Task Changelog Changelog for Task Frends.Odoo.Request. ### \[1.1.0] - 2024-08-23 #### Changed * Updated the Newtonsoft.Json package to version 13.0.3. ### \[1.0.0] - 2024-05-30 #### Changed * Initial implementation of Frends.Odoo.Request --- # 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.frends.com/tasks/tasks/odoo/request.md?ask=&goal= ``` `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.