Retry sync log

Re-enqueue a single failed sync log entry for another attempt. The underlying retry uses the same idempotency key so successful records are not duplicated. Returns 400 if the entry is not in a retryable state (permanent failure, already succeeded, or the target resource has since been deleted).

Related endpoints

• POST /integrations/{provider}/activate — Activate integration
• POST /integrations/{provider}/deactivate — Deactivate integration
• GET /integrations/{provider} — Get integration status
• POST /integrations/{provider}/test — Test integration credentials
• POST /integrations/{provider}/sync — Trigger manual sync
• GET /integrations — List all integrations
• PUT /integrations/{provider}/status — Update integration status
• PUT /integrations/{provider}/sync-toggle — Toggle integration sync

Common errors

• 400 invalid_request — malformed payload or failed validation.
• 404 resource_missing — the referenced resource does not exist or is not visible to your key.

Idempotency

Pass an Idempotency-Key header (UUID v4 recommended) to make retries safe. Keys are valid for 24 hours; see the idempotency guide.

curl -X POST "https://api.revkeen.com/v2/integrations/practicehub/sync-logs/00000000-0000-0000-0000-000000000000/retry" \  -H "x-api-key: $REVKEEN_API_KEY"

{
  "success": true,
  "data": null
}