Upsert FAQ | Gorilla Dash

curl -X PUT https://api.gorilladash.com/api/v1/website-content/websites/%7BWEBSITE_ID%7D/faqs/upsert \
     -H "GorillaDash-Api-Key: {{API_KEY}}" \
     -H "GorillaDash-Api-Secret: {{GD_RESTFUL_SECRET}}" \
     -H "Content-Type: application/json" \
     -d '{
  "faq_category_id": 14,
  "question": "Where are you?",
  "answer": "<p>Melbourne.</p>",
  "slug": "where-are-you",
  "sort": 3
}'

{
  "success": true,
  "status": 201,
  "data": {
    "id": 130,
    "website_id": 206,
    "faq_category_id": 14,
    "slug": "where-are-you",
    "question": "Where are you?",
    "answer": "<p>Melbourne.</p>",
    "sort": 3,
    "created_at": "2026-10-07T01:20:00+00:00",
    "updated_at": "2026-10-07T01:20:00+00:00"
  }
}

Creates the faq, or updates the one with the same slug. Needs a key with Website Content: Read and Write (website-content:write).

The body and rules are the same as Create FAQ. Sending an identical payload again writes nothing: no duplicate, the id is kept and updated_at does not change, so a migration can be re-run safely.

The match is on the slug you send, or on the slug of the question when you send none. Without a slug, rewording a question changes its slug and creates a new FAQ, so send a stable slug if questions may be reworded.

Request

This endpoint expects an object.

faq_category_idintegerRequired

questionstringRequired

answerstringRequired

slugstringRequired

sortintegerRequired

Response

Created

successboolean

statusinteger

dataobject

Headers

Request

Response