admin
notification-rules

Validate Rule

Check a candidate document without storing it.

A document that does not validate is a 422 naming the path in the document that is wrong, which is the same refusal a save gives — so an operator drafting a rule through the MCP fails here rather than discovering it at write time. A 200 with warnings means the document is well formed and still cannot notify anyone: savable, not activatable.

explanation names no recipients: this route names no organization to resolve them against. For the same reason it can check neither that a named on-call list exists nor that a website-lead rule names only people that notification may reach; a save does both.

post/admin/notifications/rules/validate

Request

  • Base URL
    https://api-docs.upsmith.com (the document declares no server; this is the origin it was published from)
  • Auth
    • API key in header x-api-key
    • or HTTP bearer

Headers

organization-idstring nullable
timezonestring
x-user-idstring nullable
x-actor-emailstring nullable
x-request-sourcestring nullable
x-operation-idstring nullable
x-commit-messagestring nullable
x-confirmation-idstring nullable
x-chat-idstring nullable

Request body

decisionobject required
event_typesstring[]

Response

Successful Response

validboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.