Webhooks · Batch completion notification

    Your finished batches, reported to your application

    As soon as a classification batch finishes, your server receives a signed JSON message: batch ID, number of items and errors, end date and, for API batches, the results URL. No more polling the API: you fetch the results at the right time.

    Notification when the batch ends
    Up to 3 attempts
    JSON {event, data, timestamp}
    HMAC-SHA256 signature
    CrossbordIA — Webhook log
    bulk.completed200 OK
    { "event": "bulk.completed", "data": { "job_id": "j_8f3k", "total": 24, "errors": 1 } }
    142ms14:32:18
    bulk.api.completed200 OK
    { "event": "bulk.api.completed", "data": { "job_id": "j_m7p1", "total": 12, "failed": 0 } }
    89ms13:45:02
    bulk.completed502
    { "event": "bulk.completed", "data": { "job_id": "j_q2w9", "total": 18, "errors": 0 } } → attempt 1/3
    3012ms12:30:10
    bulk.completed200 OK
    { "event": "bulk.completed", "data": { "job_id": "j_q2w9", "total": 18, "errors": 0 } } → attempt 2/3 ✓
    155ms12:30:14
    3
    Delivery attempts
    10 s
    Response timeout per attempt
    HMAC
    SHA-256 signature
    JSON
    Envelope {event, data, timestamp}
    Features

    Reliable, verifiable notifications

    Your system knows when a batch is ready and can prove the message really comes from CrossbordIA.

    Batches

    Batch completion

    bulk.completed for batches started from the application (ID, batch name, number of items, errors, end date); bulk.api.completed for API batches, with the results URL.

    Standard

    Stable JSON

    Every delivery follows the same format: { event, data, timestamp }. The X-Webhook-Event header indicates the event.

    Reliability

    Up to 3 attempts

    Immediate delivery, then retries at +1 s and +4 s if your server responds 5xx, does not respond within 10 s or is unreachable. A 4xx response stops the retries.

    Security

    HMAC-SHA256 signature

    Each URL has its own secret (whsec_…), shown only once. Recompute the HMAC-SHA256 of the received body and compare it with the X-Webhook-Signature header.

    Tracking

    Log per URL

    For each attempt: date, event, attempt number, HTTP status, latency and result. Account menu > Webhooks.

    Flexibility

    Multiple URLs

    Add several HTTPS URLs and enable or disable each one separately; each receives both events.

    Integration

    Set up your webhooks in 4 steps

    A few minutes of setup, then a notification for every finished batch.

    01

    Add the URL

    Account menu > Webhooks: enter an HTTPS URL. A secret is generated.

    02

    Copy the secret

    It is shown only once. Use it on your server to verify X-Webhook-Signature.

    03

    Receive the notification

    For every finished batch, your server receives a JSON POST {event, data, timestamp}.

    04

    Respond 2xx

    A 2xx response confirms receipt. On a 5xx or no response within 10 s, two retries follow (+1 s, +4 s).

    Ready to automate?

    Get notified when each batch finishes

    Your systems receive a signed notification as soon as a batch finishes, then fetch the justified codes and pending questions at the right time.

    HMAC-SHA256 · 3 attempts · 10 free trial credits