Knock

Knock Schedules API

The Schedules API from Knock — 3 operation(s) for schedules.

Documentation GitHub OpenAPI

Operations 6

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /v1/objects/{collection}/{id}/schedules List an object's schedules · List object schedules #

Ask an LLM

“Which recurring notifications are scheduled for an object?”

“Can I filter an object's schedules by workflow?”

Tell an agent

List schedules for object {id} in {collection}.

Show {collection}/{id} schedules for workflow {workflow}.

DELETE /v1/schedules Delete schedules · Delete schedules #

Ask an LLM

“How do I stop and remove schedules permanently?”

“Can deleted schedules be restored?”

Tell an agent destructive · confirm first

Delete schedules {schedule_ids}.

Permanently remove these schedules: {schedule_ids}.

GET /v1/schedules List schedules for a workflow · List schedules #

Ask an LLM

“Which schedules exist for a given workflow?”

“Can I narrow a workflow's schedules to certain recipients or a tenant?”

Tell an agent

List schedules for workflow {workflow}.

Show workflow {workflow} schedules for recipients {recipients}.

POST /v1/schedules Schedule a workflow for recipients · Create schedules #

Ask an LLM

“How do I schedule a recurring digest for a set of users?”

“Can I create a one-time scheduled notification at a specific time?”

Tell an agent

Schedule workflow {workflow} for {recipients} repeating {repeats}.

Create a one-time schedule of {workflow} for {recipients} at {scheduled_at}.

PUT /v1/schedules Update existing schedules · Update schedules #

Ask an LLM

“How do I change the timing of schedules I already created?”

“Can I apply the same new data to several schedules at once?”

Tell an agent

Update schedules {schedule_ids} to run at {scheduled_at}.

Change the repeat rules on schedules {schedule_ids} to {repeats}.

GET /v1/users/{user_id}/schedules List a user's schedules · List user schedules #

Ask an LLM

“What scheduled notifications does a particular user have?”

“Can I filter a user's schedules by tenant?”

Tell an agent

List schedules for user {user_id}.

Show user {user_id}'s schedules for workflow {workflow}.

Documentation

https://docs.knock.app/api-reference/workflows

https://docs.knock.app/send-notifications/triggering-workflows/api

https://docs.knock.app/api-reference/users

https://docs.knock.app/api-reference/messages

https://docs.knock.app/api-reference/objects

https://docs.knock.app/api-reference/tenants

https://docs.knock.app/api-reference/schedules

https://docs.knock.app/concepts/schedules

https://docs.knock.app/api-reference/audiences

https://docs.knock.app/api-reference/channels

https://docs.knock.app/api-reference/providers

https://docs.knock.app/api-reference/integrations

https://docs.knock.app/api-reference/bulk_operations

https://docs.knock.app/mapi

https://docs.knock.app/developer-tools/management-api

Specifications

https://raw.githubusercontent.com/api-evangelist/knock-app/refs/heads/main/openapi/knock-app-schedules-api-openapi.yml

Schemas & Data

https://raw.githubusercontent.com/api-evangelist/knock-app/refs/heads/main/json-schema/knock-workflow-trigger-schema.json

https://raw.githubusercontent.com/api-evangelist/knock-app/refs/heads/main/json-schema/knock-message-schema.json

Other Resources

https://raw.githubusercontent.com/api-evangelist/knock-app/refs/heads/main/examples/knock-trigger-workflow-example.json

https://raw.githubusercontent.com/api-evangelist/knock-app/refs/heads/main/examples/knock-identify-user-example.json

https://raw.githubusercontent.com/api-evangelist/knock-app/refs/heads/main/examples/knock-create-schedule-example.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/knock-app:knock-app-schedules-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Knock App Schedules API
  version: '1.0'
  contact:
    name: Knock
    url: https://knock.app
  license:
    name: Proprietary
  description: 'Operations tagged Schedules across 3 of this provider''s published API definitions: knock-objects-api-openapi.yml, knock-schedules-api-openapi.yml, knock-users-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.knock.app
  variables: {}
security:
- BearerAuth: []
tags:


# --- truncated at 32 KB (70 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/knock-app/refs/heads/main/openapi/knock-app-schedules-api-openapi.yml