Knock Message types API
A message type allows you to specify an in-app schema that defines the fields available for your in-app notifications.
Knock Message types API is one of 35 APIs that Knock publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 2 JSON Schema definitions.
Tagged areas include Message types. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.
This API exposes 4 operations across 3 paths, and defines 14 schemas. It is described by OpenAPI 3.0.3, 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 Message types API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (BearerAuth).
By default, every request must be authenticated.
BearerAuth— Knock API key as a Bearer token. Use a public key (pk...) for client-side requests or a secret key (sk...) for server-side.
Paths & Operations 4
Across 3 paths, the API surfaces 4 operations — 2 GET, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
A message type allows you to specify an in-app schema that defines the fields available for your in-app notifications.
Schemas 14
The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are MessageType (15 properties), MessageTypeImageField (7 properties), MessageTypeRequest (6 properties), MessageTypeButtonField (6 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.