AsyncAPI channel · Credilinq.ai
· CrediLinq Webhooks
{redirect_url}
Channel address
{redirect_url}
Parameters
redirect_url— The partner-configured webhook URL registered with CrediLinq support.
Operations
receive
receiveEvents
Messages
DRAWDOWN_INITIATED
Drawdown/Loan is initiated
Content-Type:
DRAWDOWN_APPROVED
Drawdown/Loan is approved
Content-Type:
DRAWDOWN_DISBURSED
Drawdown/Loan is disbursed
Content-Type:
DRAWDOWN_PAYMENT_VERIFIED
Drawdown/Loan payment is verified
Content-Type:
DATA_PROCESSING_COMPLETED
Customer Data Processing Completed
Content-Type:
DATA_PROCESSING_FAILED
Customer Data Processing Failed
Content-Type:
CUSTOMER_KYC_ACCEPTED
Customer's KYC is accepted
Content-Type:
CUSTOMER_KYC_REJECTED
Customer's KYC is rejected
Content-Type:
CUSTOMER_APP_ACCEPTED
Customer's KYC Application is accepted and final credit limits assigned
Content-Type:
CUSTOMER_APP_REJECTED
Customer's KYC Application is rejected
Content-Type:
DIRECTOR_SIGNATURE_UPDATED
A director signed the Loan Agreement
Content-Type:
LOO_AGREEMENT_SIGNED
All directors completed signature on Loan Agreement
Content-Type:
CREDIT_LINE_UPDATED
Customer's credit line changed
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 Agent Skill and MCP server surfaces of the same providers.
Work with this as data
Every channel here is available over the APIs.io API and to AI agents over MCP.