Skip to main content
Developer REST APIOpenAPI 3.1 Spec

REST API Reference (v1 / v2 Architecture)

Comprehensive endpoint documentation for programmatic candidate SKU ingestion, evaluation trigger, and report retrieval.

DDarryl (Platform Lead)
Published:
Updated:
6 min read

The MeritSKU Developer REST API v2 provides high-throughput programmatic access to candidate intake, unit economic calculations, evidence validation, and report syndication for agencies, ERPs, and custom inventory tooling.

Cited Claim IDs:PUB-CLM-013

1. Base URLs & Versioning Header

Production API Base: https://api.meritsku.com/v2

All requests must include the Authorization header and set Accept: application/json.

2. SKU Evaluation Endpoints (/api/v2/skus)

POST /api/v2/skus: Ingests a new candidate SKU for evaluation.

GET /api/v2/skus/{skuId}: Retrieves the current status, evidence items, and calculated landed cost factors.

BASHget-sku.sh
curl https://api.meritsku.com/v2/skus/sku_01jm8v4p2x9z \
  -H "Authorization: Bearer msku_live_mock_5a8f12c9b4e3"

3. Decision Report Endpoints (/api/v2/reports)

GET /api/v2/reports/{reportId}: Returns the complete MeritScore, confidence breakdown, 9-cell CM2 matrix, and actionable verdict.

4. Standard Error Response Codes

The API adheres strictly to standard HTTP status codes: 200 OK, 201 Created, 400 Bad Request (schema validation error), 401 Unauthorized (missing or invalid key), 404 Not Found (stealth response for unauthorized tenants), and 429 Too Many Requests.

Was this guide helpful?

Your feedback trains our editorial documentation standards.