Securing 2M+ accounts & $15B+ in assets, protected & secure·B5 Secure™ — per data-element authorization for .NET platforms

API Reference

Source-derived reference

API Reference

Open the actual B5SecurityKit reference pages already included in this website. New trust-platform contracts must be generated from build-certified endpoints before they are presented as generally available.

Production endpoints, credentials, native attestation, cloud integrations, and release certification are environment-specific.

Current package references

Build workflows

Reference contract

Request protection and response evidence

OperationMethod and pathPurpose
HealthGET /healthConfirm assigned Test Mode endpoint availability.
Evaluate trustPOST /v1/trust/decisionsEvaluate action, resource, identity, entitlement, and context.
Get evidenceGET /v1/evidence/{evidenceId}Retrieve permitted evidence for an authorized caller.
Simulate webhookPOST /v1/test/webhooks/simulateExercise signed-event delivery in Test Mode.
Signed HTTP request
curl -X POST "$B5_TEST_BASE_URL/v1/trust/decisions" 
  -H "Content-Type: application/json" 
  -H "X-B5-Tenant-Id: $B5_TENANT_ID" 
  -H "X-B5-Application-Id: $B5_APPLICATION_ID" 
  -H "X-B5-Key-Id: $B5_KEY_ID" 
  -H "X-B5-Timestamp: $timestamp" 
  -H "X-B5-Nonce: $nonce" 
  -H "X-B5-Content-SHA256: $digest" 
  -H "Authorization: B5-HMAC-SHA256 $signature" 
  --data "$body"
Truth-in-labeling: this is a reference starter. The authoritative API contract must be generated and published from build-certified B5 endpoints.
Release boundary: Production endpoints, credentials, native attestation, cloud integrations, and release certification are environment-specific.
Developer Relations

Talk to a human.

Get architecture guidance, Test Mode access, integration review, or help choosing the right B5 identity and authorization pattern.

Scroll to Top