Submit a public form
Send a public marketing or enquiry form to Merion's CRM bridge.
What you'll do
- Choose the form key supplied for your approved integration
- Send fields as a JSON object
- Handle 201, 422 and 429 responses safely
- Pass a request ID when you need end-to-end support tracing
4 min
Contract
The public Forms API accepts an approved form key at POST https://api.merion.com.au/public/forms/{key}. It is unauthenticated, uses per-IP throttling, and is intended for form capture rather than general CRM automation. Confirm the accepted key and fields with Merion before integrating.
Request
Place submitted values under fields. Add a unique, printable X-Request-ID if you need to correlate a submission with the API response and support logs. Do not send credentials, payment-card data, or any fields that the form contract does not require.
curl -X POST https://api.merion.com.au/public/forms/contact \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'X-Request-ID: contact-20260729-001' \
-d '{
"fields": {
"name": "Jordan Avery",
"email": "[email protected]",
"message": "Please contact me about a recovery matter."
}
}'Responses
A successful human submission returns 201 Created with a data envelope. Invalid fields return 422 with field-level detail; correct the values rather than retrying unchanged. Rate limiting returns 429; respect the response before attempting another submission. The API echoes the request ID as X-Request-ID and returns X-Response-Time-Ms for traceability.
Availability boundary
Public form intake does not expose debt, payments, reporting, webhook registration, API-key management, or third-party accounting integrations. For authenticated portal and staff endpoints, use the current API reference and OpenAPI contract.
Key takeaways
- POST /public/forms/{key} is the public integration endpoint
- Nest submitted values under fields
- Use X-Request-ID for correlation without sending sensitive content in it
- Treat 422 as a correction path and 429 as a backoff signal
FAQ
Which keys can I use?
Only keys provisioned by Merion for the relevant approved form. Do not probe for keys or rely on undocumented names.
Can I retry every failure?
No. Correct 422 validation failures first; back off after 429 responses. Never retry a submission blindly if that could create a duplicate enquiry.
Where do I find the complete contract?
Use the live OpenAPI document and interactive API reference, which are the source of truth for currently exposed endpoints.
Copy, paste, ship
Grab the API reference and OpenAPI spec, then wire up a resilient integration.