SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

PAPI Activation Endpoint Not Supported for Custom Functions

Question

When I try to activate a custom Destination Function for an audience using the Segment Public API, I receive the error: "Creating an Activation for a Destination Function is not supported in this Workspace". How can I get my custom function to start syncing with my audience?

 

Product

Twilio Segment 

 

Environment

Segment Console

 

Answer

Custom Destination Functions in Segment are different from standard Actions-based destinations. The Public API activation endpoint is only supported for standard Actions-based destinations, not for custom Destination Functions.

If you attempt to use the API to activate a custom function, you will receive the error: "Creating an Activation for a Destination Function is not supported in this Workspace".

To connect a custom Destination Function to an audience and start syncing data:

  1. Use the Segment Engage UI to attach the custom function to your audience.
  2. Once connected via the UI, the function will automatically receive audience sync data through its configured pipeline.

There is no separate activation step required or supported via the Public API for custom functions.

 

If you have already connected your custom function in the UI and are not seeing syncs:

  • Ensure the function is published and enabled.
  • Confirm the audience is active and has members.
  • Check for any errors in the function’s logs or configuration.
  • If issues persist, gather the function name or ID and any relevant logs, and reach out to support for further troubleshooting.

 

Additional Information 

  • API-based activation is only available for standard Actions-based destinations.
  • For automation needs, consider using a standard Actions-based destination such as a Webhooks (Actions), which supports API activation.

 

Have more questions? Submit a request
Powered by Zendesk