AI translation

This page was translated from German with AI. If in doubt, the German original applies.

Authority side with the SDK

The calls of the authority side via AuthorityNotificationDocumentHandler and the authority directory.

The background in business terms is described in the guide Competent authority side (Authority).

Two handlers

Factory method	Handler class	Document type
client.DocumentHandler.CreateAuthorityNotificationHandler()	AuthorityNotificationDocumentHandler	Notification
client.DocumentHandler.CreateAuthorityMovementHandler()	AuthorityMovementDocumentHandler	Movement

The flow is the same as on the company side: load → set operation → SaveToZedal() → SendToDiwass(). The asynchronous feedback is the same as well — the business result appears as a new version of the same document, not as a return value. See Sending procedure.

The authority handlers load only by ZEDAL DocumentId

LoadFromZedalByNotificationId(string) and LoadFromZedalByMovementId(string) are defined only on the company handlers. On the authority handlers, the only option is

await handler.LoadFromZedal(zedalDocumentId);   // DocumentId, not string

If you pass a business number as a string here, no matching overload exists. The path from the business number to the DocumentId is described in Calls and synchronization.

Notification: the operations in detail

Decision (SetDecision)

var handler = client.DocumentHandler.CreateAuthorityNotificationHandler();
await handler.LoadFromZedal(notificationZedalDocumentId);

await handler.SetDecision(new DecisionDocumentType
{
    UserCompetentAuthorityDomainId = Sf(CompetentAuthorityDomain.WsrDispatch.ToWire()),
    NotificationDocumentId = new NotificationDocumentIdentifierType
    {
        NotificationId = Sf(notificationId),
        DocumentId     = Sf(documentId)
    },
    Decision = new DecisionType
    {
        DecisionDate          = DateUtc(2026, 9, 1),
        DecisionType_         = Sf(DiwassDecisionType.Consent.ToWire()),
        DecisionJustification = /* DescriptionType, at least one language version */
    },
    CompetentAuthoritySignature = /* SignatureType: Name, OrganizationRole, Timestamp */
});

await handler.SaveToZedal();
await handler.SendToDiwass();

How an authority is identified

You can search for authorities via the directory:

// (Code, Name) per WSR authority of a country — for selection lists
var authorities = await client.DiwassApi.AuthorityDirectoryApi.ListAuthorities("BE");

// full result list with filters; countryId is required
var activities = await client.DiwassApi.AuthorityDirectoryApi.FindActivities(
    countryId: "BE", code: "DE014");