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

Quick Start

Step 3

Quick Start

The Quick Start connects the pieces. It creates a canonical request, signs it with a test credential, sends it to a configured test endpoint, and records the correlation and evidence identifiers returned by B5.

Run the reference client

Choose the next guide

Implementation steps

Copy `b5-test-settings.json` and enter Test Mode identifiers only.
Set the secret through an environment variable, not in the JSON file.
Run the .NET, Bash, or PowerShell client against the assigned Test Mode base URL.
Verify the response correlation identifier, decision result, and evidence reference.
Run the replay and wrong-audience tests before moving to a platform-specific guide.
Runnable quick start

Make the first protected request

  1. Download the .NET sample or command-line client.
  2. Set the five Test Mode environment variables.
  3. Run the client against the assigned Test Mode base URL.
  4. Record the returned correlation and evidence identifiers.
  5. Repeat the nonce to confirm replay denial.
.NET 10 signed-request excerpt
var signed = B5RequestSigner.Sign(
    HttpMethod.Post,
    new Uri($"{baseUrl}/v1/trust/decisions"),
    body,
    tenantId,
    applicationId,
    keyId,
    secret,
    DateTimeOffset.UtcNow);

request.Headers.Add("X-B5-Timestamp", signed.Timestamp);
request.Headers.Add("X-B5-Nonce", signed.Nonce);
request.Headers.Add("X-B5-Content-SHA256", signed.ContentSha256);
request.Headers.Authorization =
    new AuthenticationHeaderValue("B5-HMAC-SHA256", signed.SignatureBase64);
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