Contently · AsyncAPI Specification

Contently Webhooks

Version

View Spec View on GitHub CompanyContent MarketingTalent MarketplaceFreelanceContent CreationPublishingEditorial WorkflowRegulated ContentComplianceAsyncAPIWebhooksEvents

AsyncAPI Specification

contently-webhooks.yml Raw ↑
generated: '2026-08-13'
method: searched
spec_type: Webhooks
source: https://contently.com/platform/talent-api/
description: >-
  The Contently Talent API emits state-change webhooks over Slack, Microsoft Teams, or raw HTTP. No
  AsyncAPI document is published — this is the webhook catalog transcribed from the Talent API product
  page, which is the only place Contently documents it.
asyncapi_published: false
asyncapi_probe:
  note: >-
    /asyncapi.yaml, /asyncapi.json and an event-catalog path were not found; no OpenAPI or AsyncAPI
    document exists on any Contently host (see well-known/contently-well-known.yml).
transports:
- slack
- teams
- http
delivery_note: >-
  Slack and Microsoft Teams are named as first-class delivery targets alongside arbitrary HTTP
  endpoints — 'Slack, Teams, raw HTTP'.
events:
- name: project.assigned
  documented_as: Project assigned
  trigger: A project is assigned to a creator
- name: draft.submitted
  documented_as: Draft submitted
  trigger: A creator submits a draft
- name: review.responded
  documented_as: Review responded
  trigger: A creator responds to review feedback on a draft
- name: payout.released
  documented_as: Payout released
  trigger: A payout is released to a contractor after approval
event_name_caveat: >-
  Contently publishes these as prose labels ('Project assigned, draft submitted, review responded,
  payout released'), NOT as wire identifiers. The dotted names above are a normalization for cataloging
  and must not be treated as the literal event type strings — Contently publishes no event-type
  vocabulary, no payload schema, no delivery/retry semantics, and no signature-verification scheme.
payload_schemas: none_published
signature_verification: not_documented
retry_policy: not_documented
notes: >-
  Threaded comments on reviews are documented to 'fire back over webhook', and the messaging endpoint
  notes 'Slack and Teams webhooks supported'. An integrator can learn that four state changes exist but
  cannot learn what any of them will send.

Work with this as data

Every AsyncAPI spec 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 asyncapi

4 MCP tools reach this
  • find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.
  • 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 AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/contently-webhooks"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"

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

Get an API key

Free tier, no email required.

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