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

The Gorilla Dash API: what it is and what you can do with it

A tour of the Gorilla Dash REST API — the base address, what every endpoint has in common, and a map of everything you can read and write.

Last updated September 2, 2026

The Gorilla Dash API lets your own systems talk to Gorilla Dash. The two things people use it for most are pushing leads in — from a website form, a landing page, an ad platform or an automation tool — and pulling data out, so a website or a reporting system always shows what Gorilla Dash holds.

It is a plain HTTPS API that speaks JSON. If your tool can send a web request with two headers on it, it can talk to Gorilla Dash. No SDK required.

One word to know before you start: a tribe is one location, branch or business unit inside your organisation. It is the word the product uses on every screen, and the API follows it — tribe_id, tribe_slug, GET /tribes. Wherever these guides say tribe, that is what they mean.

The address

Everything lives under https://api.gorilladash.com/api/v1. That host serves the API and nothing else — it is not the address you log in at.

What every call has in common

Two headers identify you: GorillaDash-Api-Key and GorillaDash-Api-Secret. See the authentication guide.
A successful call answers HTTP 201, whatever it did. This surprises people — read the responses guide before you write your error handling.
The body is always JSON, wrapped in an envelope with success, status and data.
A key only ever sees its own organisation. A tribe key only sees that tribe's contacts, leads and tribe record — shared content such as knowledge articles and the food menu still comes from the parent organisation. See the authentication guide for the full table.
Lists are paged, and take page and results_per_page.

START HERE

Call GET /api/v1/ping with your two headers before you build anything else. It answers 201 and proves your credentials work, which removes half the guesswork from every problem that follows.

Everything you can call

Each of these has its own guide in this section.

Endpoint	What it does
`POST /enquiries`	Push a lead into Gorilla Dash. The one most integrations are built around.
`GET /enquiries`	Read leads back out, filtered by date, tribe or person.
`PUT /enquiries/{id}`	Add or correct custom fields and tracking data on a lead you already sent.
`GET /enquiry-forms`	List your forms and their slugs. You need a slug before you can push a lead.
`GET /enquiry-forms/{slug}`	The fields one form expects.
`GET /people`	Your contact records, with lookup by email, mobile or id.
`POST /people/send-email`	Send a one-off email to a contact, logged in Gorilla Dash.
`GET /tribes`	Your tribes, with addresses, phone numbers and opening hours.
`GET /tribes/{id}`	One tribe, by id or slug.
`POST /tribes/search`	Nearest tribes to an address or a set of coordinates. Powers store locators.
`GET /blog-articles`	Your published blog posts, list and single.
`GET /knowledge-articles`	Your knowledge base articles, list and single.
`GET /food-menu-items`	Menu items with pricing and nutrition, list and single.
`GET /digest-posts`	Published weekly digest posts.
`GET /reviews`	Featured public Google and Facebook reviews.
`GET /media`	Images from your media library.
`GET /wordpress/tribes/{id}`	A tribe with all the page content a website template needs.
`GET /wordpress/tribes/{slug}/our-works`	A tribe's portfolio or project posts.
`GET /wordpress/tribes/{slug}/our-team`	A tribe's public team members.
`GET /ping`	Confirms your credentials work.

There is one more address, GET /corebridge/account-check, which CoreBridge itself calls while a customer connects the Gorilla Dash integration in the CoreBridge marketplace. It is not something you call yourself, and it uses a different header, so it is not documented here.

THE REQUEST-BY-REQUEST REFERENCE

These guides explain how each endpoint behaves and how to use it well. For the exact schemas, example requests and a "try it" console, see the API reference at docs.gorilladash.com.

Which guide do I need?

I want to...	Read
Send leads into Gorilla Dash	Pushing an enquiry (lead) into Gorilla Dash
Understand why two submissions became one contact	How Gorilla Dash matches an enquiry to a person
See where my leads came from	Tracking where your leads come from
Copy leads or contacts into another system	Keeping your system in sync
Show tribes, reviews or posts on a website	The tribes endpoint, and the content guides
Work out why a call is failing	How responses are shaped and what the errors mean

Before you start building

Get your API key and access token — Organisation Settings, then Connections.
Confirm the API is switched on for your organisation — Organisation Settings, then Gorilla Settings, and check Disable RESTful API is off.
Call GET /ping and confirm you get a 201.
If you are pushing leads, call GET /enquiry-forms and note the slug of the form you want to send to.

ONE SWITCH TURNS ALL OF THIS OFF

Disable RESTful API in Gorilla Settings blocks every endpoint here for your organisation and every one of its tribes, immediately, with a 403. If a working integration stops overnight, check that switch before you check anything else.

Next · APIAPI keys: where to find them and what they can see