WebService

This module creates WebService frameworks to be used globally.

The module introduces support for HTTP Request protocol. The webservice HTTP call returns the full requests.Response object.

It builds on top of webservice_core (which provides the webservice.backend model with public/username-password/API key authentication) to add OAuth2 authentication and server_environment support.

Table of contents

Configuration

Upgrade from versions prior to 18.0.2.0.1

On upgrade from a version prior to 18.0.2.0.1, a webservice.request_content_only system parameter is created automatically (see that version’s migration script) to preserve the previous default behavior of HTTP calls, which returned only the response content instead of the full requests.Response object.

If your code relies on that implicit default, keep the parameter for now. Once it’s adapted to use the full response object (see Usage), delete the parameter under Settings > Technical > System Parameters - new installs never get it set.

OAuth2 (Client Credentials)

For the Backend Application (Client Credentials Grant) flow, two extra options control how the token is requested, so that endpoints which deviate from the OAuth2 spec can still be used:

Token Request Method: POST (default) or GET. Most providers expose the token endpoint as a POST; some require a GET.
Client Authentication: how the client credentials are presented to the token endpoint:
- Client ID & Secret (HTTP Basic) (default): the client id and secret are sent as an Authorization: Basic base64(client_id:client_secret) header (client_secret_basic).
- Custom Authorization header: a static header value is sent verbatim. The Client Auth Header (default Authorization) and Client Auth Header Value are configured directly; the Client ID / Client Secret fields are not used in this case.

Example: custom Authorization header

Some providers require the credentials in a non-standard Authorization header (for instance Okta uses Authorization: SSWS <token>). Such an endpoint can be configured as:

Auth Type             = OAuth2
OAuth2 Flow           = Backend Application (Client Credentials Grant)
Token URL             = https://provider.example.com/oauth2/token
Token Request Method  = GET
Client Authentication = Custom Authorization header
Client Auth Header    = Authorization
Client Auth Value     = SSWS <token>

Creu Blanca
Camptocamp

Contributors

Enric Tobella <etobella@creublanca.es>
Alexandre Fayolle <alexandre.fayolle@camptocamp.com>

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

Current maintainers:

This module is part of the OCA/web-api project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Metadata

Release files for odoo-addon-webservice 18.0.2.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo-addon-webservice 18.0.2.1.0
File	Interpreter	ABI	Platform	Reset
odoo_addon_webservice-18.0.2.1.0-py3-none-any.whl 46.6 kB Sep 28, 2026	Python 3	none	any	Details

Release files / odoo_addon_webservice-18.0.2.1.0-py3-none-any.whl

Download URL	odoo_addon_webservice-18.0.2.1.0-py3-none-any.whl
Size	46.6 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`b4cd2c7e9765a971dbb278ceede88da918cd06b7208d91ff97b20d00118e35c9`
BLAKE2b-256 checksum How to use checksums	`ddd303461bf2eedc5accc7cff1d5ce02e6086a01ee83d2f03f4f0f327582f7c6`
Upload date	Sep 28, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.14.4`