Knock Preferences API
Preferences are a way to configure how notifications are sent to recipients. They are a set of configuration that determines whether a recipient should receive a notification for a given workflow on a specific channel.
Knock Preferences API is one of 19 APIs that Knock publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include Preferences. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.
This API exposes 20 operations across 16 paths, and defines 8 schemas. It is described by OpenAPI 3.0.0, at version 1.0.
Requests are made against a single base URL, https://api.knock.app.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Knock Preferences API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
By default, every request must be authenticated.
Paths & Operations 20
Across 16 paths, the API surfaces 20 operations — 2 DELETE, 4 GET, 14 PUT. Each is listed below with its method, path, parameters, and response codes.
Preferences are a way to configure how notifications are sent to recipients. They are a set of configuration that determines whether a recipient should receive a notification for…
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are PreferenceSetRequest (6 properties), PreferenceSet (6 properties), PreferenceSetChannelTypes (6 properties), Condition (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Knock 12
Other APIs Knock publishes across the network.