Skip to content

ReviewAsk API

Last updated: October 2026

A simple HTTPS API for tech-savvy owners and integrators. Create review asks, list them, edit scheduled ones, and cancel — with the same secret key you already use for Zapier.

Machine-readable spec: openapi.json. Manage your key and callbacks in Settings → API & callbacks (same key as Zapier).

Auth

Every request needs a Bearer token (or X-Api-Token). Keys start with ra_.

Authorization: Bearer ra_…

Your account must be on an active trial or paid plan. One key is shared with Zapier: rotating it breaks an existing Zap, and disconnecting Zapier clears the key.

Base URL

https://getreviewask.com/api/v1

Account

GET /account — business name, plan status, monthly usage and quota.

Requests

Example: create an ask

curl -X POST https://getreviewask.com/api/v1/requests \
  -H "Authorization: Bearer ra_…" \
  -H "Content-Type: application/json" \
  -d '{"name":"Alex","email":"alex@example.com"}'

Statuses

scheduled, sending, sent, queued, failed, cancelled, suppressed.

Outbound callbacks

Save an HTTPS URL with PUT /endpoints (or in Settings). We POST JSON for request.created, request.sent, request.reminded, request.cancelled, and followup.cancelled. Headers: X-ReviewAsk-Event, X-ReviewAsk-Signature (sha256= hex HMAC-SHA256 of the raw body with your signing secret). The secret is shown once when you first save (or rotate).

API key (no Zapier flip)

POST /keys creates or rotates the Bearer token without turning on automatic Zapier asks. The key is still shared with Zapier — rotating it breaks an existing Zap; disconnecting Zapier clears it. Prefer Settings → API & callbacks for day-to-day use.

Zapier / Make

The existing job-complete hook stays at /api/hooks/job-complete (and the Zapier wizard URL). Prefer POST /api/v1/requests for new integrations.

Need a hand?

Email support@getreviewask.com — we read every message.