Replaces an event subscription. Send the whole object — every field is overwritten, so an omitted filter list clears that filter.
Credentials are the one exception, and it is what makes replace safe
A read never returns clientSecret or credential header values, so the obvious GET → change a field → PUT round trip would otherwise erase them. Instead:
| You send | Result |
|---|---|
| the field omitted, or null | the stored credential is kept |
| "" (empty string) | the stored credential is cleared |
| any other value | the credential is replaced |
So a pipeline can read a subscription, edit one field and write it straight back without ever handling the secret.
Turning a subscription off, after reading it with GET
{
"name": "Order created to ERP",
"isActive": false,
"connector": "Webhook",
"baseUrl": "https://erp.example.com",
"requestUri": "/omnium/orders",
"httpVerb": "POST",
"clientSecret": null,
"requestHeaders": [
{ "key": "Authorization", "value": null },
{ "key": "X-Source", "value": "omnium" }
],
"filters": { "classNames": ["Order"], "statuses": ["Created"], "markets": ["NOR"] }
}
The nulls here are exactly what GET returned, and they leave the stored secret and the stored Authorization value untouched.
Rotating the secret — send the new value instead of the null:
{ "clientSecret": "the-new-secret-value" }
(as part of the full object — this is a replace, not a patch).
An id in the body is ignored; the one in the route wins.
Request
- Base URL: https://api.omnium.no (the document declares no server; this is the origin it was published from)
- URL: https://api.omnium.no/api/EventSubscriptions/{id}
- Auth: API key in header Authorization
Path parameters
Id of the subscription to replace.
Request body
Response
Subscription updated. Credentials are omitted from the response.
Changes
No recorded changes to this operation across all 1 revision of this API.