Forms

Use your existing form.

PINGSLAP is not a contact form builder. You generally keep your current website form and connect its webhook action, form handler, or server route to your PINGSLAP Space.

Recommended order

Use the form platform's built-in webhook feature.
Use a server-side form handler.
Use a same-origin proxy for custom browser JavaScript.
Configure receiving-server CORS only when direct browser posting is intentionally supported.

Server-to-server

Your visitor submits your website form. Your website receives the form, then your server sends a webhook to PINGSLAP.

Visitor↓Website↓PINGSLAP

Browser JavaScript

Your visitor's browser sends a request directly to PINGSLAP. This can work only when browser security rules allow it.

Visitor Browser↓PINGSLAP

Server-side webhooks are usually easier

WordPress form plugins, backend APIs, and automation tools send webhooks from a server. Server requests do not use the same CORS checks that browsers use, and your PINGSLAP webhook URL is less likely to be exposed in public page code.

When browser JavaScript makes sense

Use browser JavaScript only for low-risk experiments or when you understand how to protect the webhook URL. For production lead forms, prefer a server, WordPress webhook, automation platform, or reverse proxy.