The public API is currently read-only across Payments, Contacts, and Campaigns, and webhooks are outbound-only (payment.completed to our endpoint). That means there is no supported way to create a contact in Zeffy from a form built outside Zeffy.

The practical effect: organizations that want a custom-designed signup form on their own site have no path to get those contacts into Zeffy's CRM. The embed is the only option, so any limitation in the embed becomes a hard blocker rather than a preference.

A POST /v1/contacts endpoint — even limited to create, with support for tags or custom fields — would solve this. It would also let organizations sync contacts in from other systems, not just export them out.