Gorilla Dash

Help Centre

Guides for every part of Gorilla Dash

Step-by-step how-to guides written by the team that builds the product. Read them here, or download any guide as a PDF.

API

Sending an email to a contact

Download PDF

POST /people/send-email sends a one-off email to one of your contacts from your own sending domain, and logs it in Gorilla Dash so the send is recorded against them.

Last updated September 2, 2026


POST https://api.gorilladash.com/api/v1/people/send-email sends a single email to one contact. Gorilla Dash supplies the sender identity — the from name, the reply-to address and your organisation's sending domain, or the tribe's where you have named one — and logs the send, so it appears in Gorilla Dash rather than vanishing into your own mail server.

It is for transactional, one-to-one messages: a booking confirmation, a follow-up triggered by something in your own system. It is not a campaign tool — use Marketing Automations for anything that goes to more than one person.

The payload

FieldRequiredNotes
person_idYesThe contact to email. From GET /people.
subjectYesThe subject line.
bodyYesThe complete HTML body of the email, sent exactly as you supply it.
tribe_idNoSend as this tribe. Organisation keys only.
tribe_slugNoSame, by slug.
global_idNoSame, by the tribe's global id.

{"person_id":48210,"subject":"Your quote is ready","body":"<p>Hi Sam, your quote is attached to your account.</p>"}

On a tribe key the tribe is always that key's own tribe, and the three tribe fields are ignored. On an organisation key, name a tribe with any one of them; the tribe must be active. Name none and the email goes out as the organisation.

What comes back

A 201 with {"log_uuid":"..."} — the identifier of the log entry created for this send. Keep it against your own record if you want to trace a specific message later.

Errors

CodeCause
404The contact does not exist, is not yours, has no email address, or the tribe you named is not an active tribe in your organisation.
422A required field is missing.
403The RESTful API is switched off for your organisation.

A contact with a blank email address is treated as not found, not as a validation error. If you are sending in bulk, check for an email address on your side first so a run of 404s does not look like a scoping problem.

Things to be careful about

THERE IS NO DUPLICATE PROTECTION HERE
Unlike the enquiry push, this endpoint does not recognise a repeat. Call it twice and the contact gets two emails. If your integration might retry after a timeout, record what you have sent on your side before you send it.
  • Each call sends one email. Sending to a hundred people is a hundred calls, and the rate limit applies.
  • The contact does not have to have opted in to marketing for this to send, so it is on you to only use it for messages the contact is expecting.
  • body is the complete HTML body, sent exactly as you supply it. There is no Gorilla Dash template around it — no header, no footer, no styling, and a plain-text body will render as one run-on line. Send finished HTML.
  • There is no attachment support on this endpoint.
WHEN TO USE SOMETHING ELSE
One person, triggered by an event, expected by the recipient: this endpoint. Many people, on a schedule, or anything a recipient might want to unsubscribe from: build it in Marketing Automations instead, where consent and unsubscribes are handled for you.
Next · APIYour tribes: the tribes endpoint