TIN verification request completed

webhook

tinVerificationFinished

Fired when a TIN verification request finishes processing (either successfully or with an error). The payload contains the request ID and final status. Use GET /tin_verifications/{id} to fetch the full results.

Payload

Notification that a TIN verification request has reached a terminal state. Use GET /tin_verifications/{id} to fetch the full results.

code

string

required

Defaults to tin_verification.finished

Code that describes the event.

triggered_at

integer

required

Unix timestamp indicating when the event was triggered.

data

object

required

Minimal payload with the request ID and final status. Fetch full results via GET /tin_verifications/{id}.

Headers

X-B2Brouter-Signature

string

required

Contains a signature to verify the authenticity and integrity of the request.
The signature is generated using the HMAC-SHA256 algorithm with a payload composed of the timestamp and the JSON data.
Format: t={timestamp},s={signature}.

X-B2Brouter-Delivery-Id

string

required

Identifies the delivery. Every attempt of the same delivery carries the same value, so use it to discard
a delivery you have already processed. Treat it as an opaque string. It is not covered by
X-B2Brouter-Signature, so do not rely on it to detect replayed requests.

X-B2Brouter-Delivery-Attempt

string

required

Attempt number of this delivery: 1 for the first attempt, then 2, 3, ... for each automatic retry.
A delivery resent manually from the B2Brouter delivery log repeats the number of its last attempt, which
is 0 if it was never attempted automatically.

Responses

200

Return a 200 status to indicate that the data was received successfully

404

The webhook URL could not be reached. Ensure the URL is correct and reachable.