Skip to content

Connect from a desktop application

Overview

A desktop application can call Sigabill APIs as long as it authenticates against Azure AD B2C.

This guide complements the Azure AD B2C connection guide. For detailed WPF implementation steps, see the Microsoft documentation.

Information to provide for onboarding

Before activation, send the Sigabill team:

  1. the application type: Desktop;
  2. the target environment: devtest, staging, or production;
  3. the required scopes;
  4. the technical contact responsible for the integration.

The redirect URI is standard for desktop applications — you do not need to choose one (see section below).

Redirect URI

You do not need a web page, nor do you need to choose a URI.

The standard redirect URI for desktop applications is an endpoint belonging to Sigabill's Azure AD B2C tenant:

https://<sigabill-tenant>.b2clogin.com/oauth2/nativeclient

Sigabill configures this URI when registering your application. You will receive the exact value along with your integration credentials.

On your side, you simply set it in your MSAL configuration. MSAL intercepts the redirect automatically — no web server is required.

Call sequence

  1. The user signs in through Azure AD B2C (system browser opened by MSAL).
  2. MSAL intercepts the redirect and retrieves the access_token.
  3. The application calls Tenant Manager to retrieve accessible companies.
  4. The user selects the target tenant.
  5. The application calls Sigabill APIs with Authorization: Bearer <access_token>.