Send an enquiry from your own website or CRM
The one write endpoint: a lead from your website form, your CRM or an agent's system lands in the same pipeline as one a staff member typed.
Reading Pallara is open across 51 resources. Writing is deliberately narrow — one documented action today, creating an enquiry — because creating an enrolment has to pass seat limits, the Public Trust payment gate and portal provisioning, and a generic table writer walks past all of that silently. More actions are added one at a time, with their rules intact.
Post an enquiry
curl -X POST https://<your staff host>/api/bulk/enquiries \
-H "Authorization: Bearer $PALLARA_TOKEN" \
-H "Idempotency-Key: 7c1f-website-form-84213" \
-H "Content-Type: application/json" \
-d '{"firstName":"Aroha","lastName":"Ngata","email":"[email protected]","phone":"021 555 0134","message":"Asking about the March intake"}'It arrives in Admissions → Enquiries exactly as a staff-typed one does, and follows the same pipeline from there.
Three things that will save you a support email
- An email address or a phone number is required. One with neither is refused with
no_contact— a lead nobody can reply to is not a lead. - `Idempotency-Key` is honoured. If your request times out and you send it again with the same key, the original enquiry is replayed rather than a duplicate created. Use something stable and specific to the submission, not a timestamp.
- Leads are attributed to the credential that sent them, so you can tell website traffic from an agent's feed without asking the sender to declare which they are. Mint a separate token per source and name it after the source.
NoteIf a different action is on your critical path, say which one. What becomes writable next is decided by what integrators actually need, not by filling in a table.
Full request and response detail, including errors, is in the API reference.
Was this guide helpful?