AsyncAPI channel · Basecamp · Basecamp Webhook Events

/webhook

The HTTPS endpoint on the subscriber's server that receives webhook notifications from Basecamp. Basecamp sends HTTP POST requests with JSON payloads. Subscribers should respond with a 2xx status code within a reasonable timeout to acknowledge receipt. Failure to respond with 2xx after 10 attempts will cause Basecamp to deactivate the webhook.

Open source AsyncAPI → All Basecamp channels Basecamp provider profile
Provider: Basecamp AsyncAPI: v2.6.0 Spec: Basecamp Webhook Events Operations: 1 Messages: 37

Channel address

/webhook

Operations

publish
receiveBasecampWebhook
Receive a Basecamp webhook event notification

Messages

message_created
A new message was created on a message board
Content-Type:
message_updated
An existing message was updated
Content-Type:
message_archived
A message was archived
Content-Type:
message_trashed
A message was moved to trash
Content-Type:
todo_created
A new to-do was created
Content-Type:
todo_updated
An existing to-do was updated
Content-Type:
todo_completed
A to-do was marked as completed
Content-Type:
todo_uncompleted
A to-do was marked as incomplete
Content-Type:
todo_archived
A to-do was archived
Content-Type:
todo_trashed
A to-do was moved to trash
Content-Type:
todolist_created
A new to-do list was created
Content-Type:
todolist_updated
An existing to-do list was updated
Content-Type:
todolist_archived
A to-do list was archived
Content-Type:
todolist_trashed
A to-do list was moved to trash
Content-Type:
document_created
A new document was created in a vault
Content-Type:
document_updated
An existing document was updated
Content-Type:
document_archived
A document was archived
Content-Type:
document_trashed
A document was moved to trash
Content-Type:
comment_created
A new comment was posted on a recording
Content-Type:
comment_updated
An existing comment was updated
Content-Type:
comment_trashed
A comment was moved to trash
Content-Type:
card_created
A new card was created on a card table
Content-Type:
card_updated
An existing card was updated or moved
Content-Type:
card_archived
A card was archived
Content-Type:
card_trashed
A card was moved to trash
Content-Type:
schedule_entry_created
A new schedule entry was created
Content-Type:
schedule_entry_updated
An existing schedule entry was updated
Content-Type:
schedule_entry_archived
A schedule entry was archived
Content-Type:
schedule_entry_trashed
A schedule entry was moved to trash
Content-Type:
upload_created
A new file upload was created in a vault
Content-Type:
upload_updated
An existing upload was updated
Content-Type:
upload_archived
An upload was archived
Content-Type:
upload_trashed
An upload was moved to trash
Content-Type:
question_answer_created
A new answer was submitted to an automatic check-in question
Content-Type:
question_answer_updated
An answer to an automatic check-in question was updated
Content-Type:
question_paused
An automatic check-in question was paused
Content-Type:
question_resumed
A paused automatic check-in question was resumed
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.