Dibk.Oppsamlingsregister.IngestApi.Client 1.0.17

Dibk.Oppsamlingsregister.IngestApi.Client

A lightweight .NET client for sending batches to the Oppsamlingsregisteret Ingest API. It is designed for use with IHttpClientFactory, handles multi-file uploads (multipart/form-data), and provides resilient retries with exponential backoff + jitter. Authentication/authorization is expected to be handled by the Azure resource itself (for example RBAC on the managed identity or by exposing the API only inside a private VNet), so the client does not attach tokens or API keys.

Contents

• Installation
• Target framework
• Quickstart
  • Via appsettings.json
  • Programmatic configuration
• Usage
• Configuration options
• Error handling
• Publishing to NuGet
• Notes
• License

Installation

dotnet add package Dibk.Oppsamlingsregister.IngestApi.Client

Target frameworks

• .NET 8.0
• .NET 10.0

Quickstart

Via appsettings.json

OppsamlingsregisterIngestApiOptions can be bound directly from configuration. The DI extension registers an HttpClient, binds the options, and sets sensible defaults (BaseAddress, Accept: application/json, Timeout).

{
  "OppsamlingsregisterIngestApiOptions": {
    "BaseUrl": "https://ingest.example.com",
    "RetryCount": 3,
    "RetryBaseDelayMs": 250
  }
}

// Program.cs
builder.Services.AddOppsamlingsregisterIngestApiClient(builder.Configuration);
// IOppsamlingsregisterIngestApiClient can now be injected

Programmatic configuration

You can also configure the client without appsettings by passing an Action<OppsamlingsregisterIngestApiOptions>.

builder.Services.AddOppsamlingsregisterIngestApiClient(opts =>
{
    opts.BaseUrl = "https://ingest.example.com";
    opts.RetryCount = 3;
    opts.RetryBaseDelayMs = 250;
});

Usage

IOppsamlingsregisterIngestApiClient exposes SendBatchAsync to submit a batch of files. The client builds a multipart/form-data request containing metadata (archiveReference, distributionSubmittalType, sentAtUtc) alongside every file in the IngestRequest.

using Dibk.Oppsamlingsregister.IngestApi.Client;
using Dibk.Oppsamlingsregister.IngestApi.Client.Models;

public class MyService(IOppsamlingsregisterIngestApiClient client)
{
    public async Task RunAsync(CancellationToken ct)
    {
        var request = new IngestRequest
        {
            ArchiveReference = "ar-2025-09-08-001",
            DistributionSubmittalType = "demo",
            Files = new[]
            {
                new IngestFilePart
                {
                    FileName = "data.xml",
                    ContentType = "application/xml",
                    Metadata = new Dictionary<string, string>
                    {
                        ["source"] = "client-demo",
                        ["note"] = "optional"
                    },
                    OpenReadAsync = _ => Task.FromResult<Stream>(File.OpenRead("data.xml"))
                },
                new IngestFilePart
                {
                    FileName = "map.gml",
                    ContentType = "application/gml+xml",
                    OpenReadAsync = _ => Task.FromResult<Stream>(File.OpenRead("map.gml"))
                }
            }
        };

        await client.SendBatchAsync(request, ct);
    }
}

IngestFilePart.OpenReadAsync must return a new stream for every attempt (retries included), therefore it is a Func<CancellationToken, Task<Stream>>. Add per-file metadata using the Metadata dictionary when needed.

Configuration options

All settings live on OppsamlingsregisterIngestApiOptions:

Error handling

• Transient failures (HTTP 5xx/408, network/timeout exceptions) trigger exponential backoff with jitter. The number of attempts is controlled by RetryCount.
• Non-transient failures (or when the retry budget is exhausted) throw IngestApiException with the HTTP status and any raw response payload as text.
• On success the API is expected to return 204 No Content, so SendBatchAsync simply completes.

Publishing to NuGet

Tag a release:

git tag ingest-client_1.2.3
git push origin ingest-client_1.2.3

Notes

• Authentication: access control should be enforced at the Azure resource (e.g. RBAC on the managed identity or private endpoints inside a VNet). The client intentionally omits auth headers/tokens.
• Models: see IOppsamlingsregisterIngestApiClient, IngestFilePart, and IngestRequest for the payload structure.
• DI registration: use AddOppsamlingsregisterIngestApiClient(...) with either the IConfiguration or Action<OppsamlingsregisterIngestApiOptions> overload.

License

MIT