Developers
The public endpoints, their exact contracts, the error catalogues and the per-platform recipes.
Orders API (generic connection)The HTTP endpoint that records an order — or a cart someone has started to pay for — from any tool. Exact contract, field reference, responses, the 422 error catalogue and which contact level each payload creates.Capture points APIThe public endpoint that turns a submission from another platform into contact + consent. Exact contract, fields, responses, the August 2026 change and which contact level each submission creates.Connecting through Zapier or MakeHow to push every order to the generic connection without writing code, with the field mapping and the consent-as-text trap.Stores and payment gatewaysConcrete recipes for PrestaShop, Wix, Squarespace, Shopify and Stripe — all of them into the generic connection, each with its own traps.WooCommerceThe native connector with signed webhooks, the checkout consent field, and the snippet that carries the link token all the way to the order.Connecting CalendlyThe native Calendly integration — what it announces, how the notifications arrive on each Calendly plan (instantly or every 5 minutes), how Konverda recognises the person (by the link it sent them, then phone, then email), what to do with bookings that match nobody, the rule that tags, and what a flow can do with Calendly (send the booking link, cancel, mark a no-show).Connecting StripeThe native Stripe integration — what it announces (payments, subscription invoices and refunds), why Konverda only reads and never moves money, how it recognises the person (phone, then email), what payments without a contact are, and how to build the rule that thanks somebody after a payment.