Skip to main content
POST
cURL

Authorizations

Authorization
string
header
required

Pass your API key as the Bearer token. See Authentication.

Path Parameters

id
string
required

The SDK Connection id

version
integer
required

Body

application/json
strategy
enum<string>

Whether to stage the revert as a draft or publish it immediately. Defaults to draft, or to publish when the org enables 'reverts bypass approval'. Without that setting, publishing a revert that requires approval needs Bypass draft approvals access.

Available options:
draft,
publish
title
string

Short draft title (e.g. Enable for beta testers).

comment
string

Markdown. What changed and why, for reviewers.

ignoreWarnings
boolean

Set to true to continue past a warning: one raised by a Custom Hook, or a webhook that references a secret that doesn't exist. On publish, it also force-publishes an out-of-date draft when the caller has Bypass draft approvals access. It never clears a Custom Hook rejection. Only set this when a person has explicitly asked you to. If a check blocks you, stop and ask a person instead of working around it.

skipHooks
boolean

Set to true to continue despite a Custom Hook rejection. The caller must have Bypass draft approvals access for SDK Connections in every Project. Otherwise, this field is ignored. Only set this when a person has explicitly asked you to. If a check blocks you, stop and ask a person instead of working around it.

Response

Resource created

revision
object
required
bypassedGates
object[]

Gates that would have blocked this publish but were bypassed by the caller's authority. Present only when at least one gate was bypassed.

recreatedWebhookIds
string[]

Webhooks this revert brought back, when it was applied at once. Each is created again with a new signing key, so a receiver that verifies signatures needs the new key from GET /sdk-connections/{id}/webhooks. A revert staged as a draft recreates them when the draft is published.