REST API

Programmatic code reviewvia HTTP

Trigger the same analysis pipeline from internal tools, release bots, or custom CI. Upload a diff or patch, poll for completion, and consume structured findings in JSON.

REST JSONAPI keyswebhooks optionalsame engine as UIidempotent jobs
How it works

Workflow

How teams wire it

  1. 1

    Issue an API key

    Create a scoped key in workspace settings and store it in your secret manager.

  2. 2

    POST review payload

    Send diff text or connected repo metadata depending on your integration shape.

  3. 3

    Poll or webhook

    Read status until completed, or register a webhook for push-style notifications.

  4. 4

    Map findings

    Translate severity and line anchors into your internal ticketing or merge gate.

Overview

When teams choose the API

GitHub is not the source of truth for every company. Self-hosted GitLab, Perforce bridges, and bespoke review queues still need the same quality bar.

The API keeps review logic out of your workers: you supply the diff and metadata, CodeCritic returns normalized findings your platform renders however you want.

Examples

Integration examples

Create a review from a diff

Exchange an API key for a review job, then fetch results.

curl -sS -X POST https://api.code-critic.com/v1/reviews \
  -H "Authorization: Bearer $CODECRITIC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "release-2026-07-12",
    "diff": "diff --git a/app/pay.rb b/app/pay.rb\n...",
    "language": "ruby"
  }'

FAQ

Common questions

Usage follows your workspace plan limits the same way as UI and GitHub-triggered reviews. Check Pricing for current quotas and overage behavior.

Related pages

WebhooksDiff reviewCI automation

Build review into your platform

Generate an API key and wire one POST from your staging pipeline to validate the JSON contract.

Integrations