New AI Agent can now build your knowledge base, connect channels and invite agents — all by chat Try it now
Help homeProductPricingBlog
Start freeLog in

Configure Custom API and event webhooks

Set up developer integrations, callback URLs, signatures, and fixed egress IPs.

Updated 2026-08-09

Walk through the demoDemo data
Channel marketplaceDemo data
Website & email3
Web Widget1 connected

A white-label chat bubble for your site

Custom API1 connected

Send and receive through your own system

Email

Bring customer email into one inbox

Social & messaging8
WhatsApp

Connect WhatsApp Business to serve customers

Messenger

Connect Facebook Pages and handle messages

Instagram DM

Receive and reply to Instagram DMs

LINE

Connect a LINE Official Account

Telegram1 connected

Connect a Telegram bot for customer messages

TikTok

Pending — subject to TikTok review and authorization

Zalo OA

Connect a Zalo Official Account

YouTube

Receive and reply to comments

Enterprise IM2
WeChat Customer Service2 connected

Connect official enterprise customer service accounts

WeComPlanned

Customer contacts, group chats, and agent collaboration

Step 1 / 8
Open the Custom API channel

Custom API channels and event webhooks are grouped as developer integrations. Pro, Enterprise, and custom plans that inherit the entitlement can create and enable them.

Custom API channels and event webhooks connect your own systems to YundaDesk. Current availability is shown on the in-product plan page.

What happens after a plan change#

If the workspace moves to a plan that no longer includes a developer-integration capability:

  • Existing configuration, signing secrets, and delivery history are preserved.
  • The corresponding Custom API channel or event webhook is disabled and stops sending new requests.
  • You can still view, disable, or delete existing configuration, but you cannot create, enable, test, replay, or rotate secrets.
  • Regaining the entitlement does not restore integrations automatically. Review the configuration and enable it manually.

Configure a callback URL#

A callback or event webhook URL must:

  • Be a public https:// URL on port 443.
  • Contain no username, password, or # fragment.
  • Match the saved allowed domain. Use an explicit, controlled wildcard when multiple subdomains are required.
  • Accept traffic from the fixed egress IPs published by YundaDesk.

After saving, use the page's test action. A successful test proves that the current request is reachable; before going live, also verify the signature, event payload, and source IP in the receiving system.

Fixed egress IPs#

YundaDesk sends Custom API callbacks and event webhooks from fixed egress IPs. The page keeps egress IPs collapsed by default. When configuring the receiver, select the blue View allowlist IPs link, then add the displayed addresses to the receiving server's allowlist.

If the page says no egress IPs have been published, contact YundaDesk support instead of allowing traffic from every source. The page may show multiple IPs; allow all of them.

Verify requests#

Verify the YundaDesk signature and timestamp in the receiving system, and use the event or delivery ID for idempotency. Do not use source IP as the only authentication control.

Use the public Custom API inbound URL shown in the product. Sending the same signed receipt again does not apply the delivery transition twice.

Troubleshoot delivery failures#

Start with the delivery status and error type on the relevant Custom API or event webhook page:

  • Plan or quota blocked: check the current plan and usage.
  • URL or domain rejected: verify HTTPS, port, domain, and URL contents.
  • Timeout or target unavailable: confirm that the target is online and allows every published egress IP.
  • Signature rejected: verify the current secret; after rotation, confirm that the receiver uses the new secret.

Temporary network or DNS failures are retried automatically. After the retry limit is reached, use the replay action provided by the product.

Didn't find your answer?

Start free and try the real product, or reach out — humans are as online as the AI.