A fast guided onboarding path for API customers. If you already know you need the first-order flow, jump straight to the docs start-here section and reuse the same steps there.
oc_live_... key and confirm the API is reachable.
GET /health and POST /v1/onboarding/demo-data, then resolve sample_customer_id and sample_order_item.sku_id.
POST /v1/orders with Idempotency-Key so retries stay safe and webhook delivery can be verified.
# GET /health
curl -sS https://api.ordercore.ai/health
Use this to confirm the API is reachable with your live key path.
export API_KEY="oc_live_..."
# POST /v1/onboarding/demo-data
SEED_JSON="$(curl -X POST 'https://api.ordercore.ai/v1/onboarding/demo-data' \
-H "X-API-Key: $API_KEY" \
-H "Content-Type: application/json" \
-d '{}')"
CUSTOMER_ID="$(printf '%s' "$SEED_JSON" | jq -r '.sample_customer_id // empty')"
SKU_ID="$(printf '%s' "$SEED_JSON" | jq -r '.sample_order_item.sku_id // empty')"
test -n "$CUSTOMER_ID" || { echo "No sample_customer_id returned by onboarding"; exit 1; }
test -n "$SKU_ID" || { echo "No sample_order_item.sku_id returned by onboarding"; exit 1; }
This removes SKU guessing and keeps the first order deterministic.
# POST /v1/orders
curl -X POST "https://api.ordercore.ai/v1/orders" \
-H "X-API-Key: $API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: first-order-001" \
-d "{\"customer_id\":\"$CUSTOMER_ID\",\"items\":[{\"sku_id\":\"$SKU_ID\",\"quantity\":1}]}"
After this flow you will have a real order in the system, a working API call, and a clear go/no-go decision.
Built for real systems: idempotent order creation, retry-safe APIs, webhook-driven integrations.
No store, no UI, no checkout flow needed. Just API.
Once the idempotent order call and the webhook confirmation succeed, you are ready for the assisted pilot.
Start 3-Day Trial