AsyncAPI channel · iContact
· iContact Webhooks
/
iContact POSTs a JSON array of event objects to the registered url. One registration carries one eventId, so a receiver may be registered several times at different paths to separate event types.
Channel address
/
Operations
receive
receiveContactCreated
When a new contact is created.
receive
receiveContactUpdated
When an existing contact is modified.
receive
receiveContactSubscribed
When a contact is subscribed to a list.
receive
receiveContactUnsubscribed
When a contact is unsubscribed from a list.
Messages
contact_created
When a new contact is created.
Content-Type:
application/jsoncontact_updated
When an existing contact is modified.
Content-Type:
application/jsoncontact_subscribed
When a contact is subscribed to a list.
Content-Type:
application/jsoncontact_unsubscribed
When a contact is unsubscribed from a list.
Content-Type:
application/jsonAbout 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 Agent Skill and MCP server surfaces of the same providers.