API
REST API
Authenticate and call the rewish public API for projects and issues.
The rewish REST API is available at your SaaS deployment under /api/v1. Create an API key under Integrations → API & Webhooks and send it as a Bearer token.
Authentication
Authorization: Bearer ntk_live_…API keys are scoped to a single workspace. Keys have administrator access to that workspace's projects and issues.
Endpoints
| Method | Path | Description |
|---|---|---|
GET | /v1/projects?organizationId=… | List projects |
GET | /v1/projects/{projectId} | Get project |
GET | /v1/issues?projectId=… | List issues |
GET | /v1/issues/{issueId} | Get issue |
POST | /v1/issues | Create issue |
PATCH | /v1/issues/{issueId} | Update issue |
DELETE | /v1/issues/{issueId} | Delete issue |
GET | /v1/webhook-deliveries?organizationId=… | List webhook delivery attempts |
POST | /v1/webhook-deliveries/{deliveryId}/retry | Retry a failed delivery |
You can also use a signed-in session cookie for the same routes when calling from the dashboard.
Example: create an issue
curl -X POST "https://app.rewi.sh/api/v1/issues" \
-H "Authorization: Bearer $REWI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"projectId": "proj_…",
"title": "Checkout button misaligned",
"description": "Reported via API",
"priority": "HIGH"
}'Webhooks
For event-driven integrations (Zapier, Make, custom servers), combine API keys with outbound webhooks. Webhook deliveries are logged and retried automatically on failure.