TechStrap.Client 0.2.2

TechStrap.Client

A small .NET client for the TechStrap support desk: submit a support ticket from your own app over the intake API, with an API key, retries and typed errors.

Install

dotnet add package TechStrap.Client

Register

Register the client once. AddTechStrapClient reads the section TechStrap (keys BaseAddress and ApiKey, plus the optional ones listed under Configuration keys), or takes a delegate.

builder.Services.AddTechStrapClient(builder.Configuration.GetSection(TechStrapClientDefaults.ConfigurationSection));

Submit

Resolve ITechStrapClient and send a SubmitTicketRequest. Supply a stable idempotency key so a retry never creates a second ticket.

var request = new SubmitTicketRequest(
    Email: "ana@example.com",
    Name: "Ana",
    Subject: "Printer on floor 2 is offline",
    Body: "It stopped answering this morning.",
    ExternalUserRef: null,
    Metadata: null);

// Keep this key and reuse it if you retry this ticket; a new key on a retry can create a duplicate.
Result<SubmitTicketResponse> result = await client.SubmitTicketAsync(request, Guid.NewGuid().ToString("N"));

Handling results

Expected failures are Result failures, never exceptions. Check IsSuccess, then read Value or the Errors.

if (result.IsSuccess)
{
    Console.WriteLine($"Ticket {result.Value.TicketNumber}");
    Console.WriteLine($"View: {result.Value.ViewUrl}");
    return 0;
}

foreach (var error in result.Errors)
{
    Console.Error.WriteLine($"{error.Code}: {error.Message}");
}

return 1;

The error codes are constants in TechStrapClientErrorCodes:

Server text reaches the Result only for a 400 or 422 (its detail and field messages); every other failure has a fixed message. Invalid options are the exception: OptionsValidationException is thrown the first time the client is used, and its message names the key and never contains the API key.

Keys

Use a Trusted key only from server-side code you control. A Public key is meant for apps you ship to customers: it can be extracted from the app by design, so the server marks the metadata it sends as untrusted and ignores ExternalUserRef. Never embed a Trusted key in an app. The key travels in the X-Api-Key header only and is never logged or put in an exception message.

Retries and idempotency

A submit is retried only when the server can recognise the repeat: the SDK sends the same Idempotency-Key on every attempt (transport errors, timeouts and the statuses 408, 502, 503 and 504 are retried, up to MaxAttempts). The server keeps a key for 24 hours.

• If you retry a failed submit yourself, supply your own stable key and reuse it. The overload without a key generates one and does not return it, so a second call can create a duplicate ticket.
• api-unavailable means the ticket may or may not have been created (the response can be lost after the server stored it). Retry with the same key and the server returns the first ticket.
• rate-limited means retry later with the same key.
• SubmitTicketOnceAsync sends exactly once and never retries.

Configuration keys

Compatibility

Targets net10.0. The package is AOT-compatible (serialization is source-generated). It is versioned in lockstep with TechStrap.Contracts. There is no attachment support yet.

More: https://github.com/Syntax-Circus/techstrap/blob/main/docs/development/CLIENT-SDK.md

Source and issues: https://github.com/Syntax-Circus/techstrap