Developers
FAQs6

Delete an FAQ entry

DELETE/support/faqs/{faq_id}

Deletes an FAQ entry. Deleted entries no longer appear in the collection and can no longer be retrieved.

Authorization

AuthorizationBearer <token>

Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.

In: header

Path Parameters

faq_id*string

Public ID of the faq, prefixed with faq_.

Header Parameters

Idempotency-Key?string

Client-generated key that makes the request safe to retry. Must be 1 to 128 characters from [A-Za-z0-9._:-]. Optional on this operation; when sent, a malformed key returns idempotency_key_invalid, and repeating the request with the same key and the same body returns the stored result with Idempotent-Replayed: true.

X-Client-Request-Id?string

Optional client-generated identifier of the request, up to 64 characters from [A-Za-z0-9._-]. Echoed back in the response and recorded in the request log; it never replaces the server-generated X-Request-Id.

Lengthlength <= 64

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/support/faqs/string"
Empty

Update an FAQ entry PATCH

Updates an FAQ entry. Only the fields present in the request are changed. Setting `position` moves the entry within its group; positions start at 1. When `group` is changed in the same request, `position` applies within the new group. Changing `status` also requires the `faqs.publish` permission. To avoid overwriting a newer version, send the `ETag` returned by the retrieve operation in the `If-Match` header. The header is optional; when it is omitted, the update is applied to the current revision.

Legal terms7

Next Page