action threatjammer_update_configuration_origin_v1_origin_put { label: "Update the configuration of an origin of the user in the region." description: "### What\nModify the configuration metadata of the origin of the user in the selected region.\n\nThe origin is a combination of protocol and domain (Ex: https://example.com) and the origin token is a special key used in conjunction with javascript library used for abuse detection. This key is owned by the user and is used to identify the origin of the request.\n Hence, the protocol and domain of the origin must be the one where the javascript is loaded.\n\n### Parameters\nIn the body of the request, add the `origin` of the user and the `config` parameter with the following format for the `origin`:1. Protocol: Can be ``http`` or ``https``.\n2. Domain: The domain of the origin.\n\nThe `config` parameter is a JSON object containing the configuration of the origin. It only accepts the existing parameters obtained from the `GET` request of the origin. If the parameter is not present in the `config` object, it will fail to store it. It's not necessary to send all the parameters, only the ones that need to be updated.\n\n### Result\nThe result is the JSON object with all the new values of the origin configuration.\n\n### Errors\n- a `404 Not Found` error if the origin token is not found.\n- a `400 Bad Request` error if the origin does not have the correct format.\n- a `400 Bad Request` error if the `config` parameter is not a JSON object or unknown parameters are sent.\n\nIt will return the API Global errors described in the API description." provider: threatjammer method: PUT path: "/v1/origin" encoding: json input: { type: "object" required: ["origin"] properties: { config: { type: "object" description: "The configuration information to store in the origin." } origin: { type: "string" description: "The origin site to modify the configruation" } } } output: { type: "object" } }