Table of Contents

Namespace Line.OpenApi.Liff

Classes

LiffClient

Facade for the LIFF management API. It wraps a single-host (api.line.me) Kiota client and provides the priority use case "list / add / update / delete LIFF apps" through thin convenience methods.

Unlike Messaging, there is no data-plane host, so no host override (BaseUrl) is needed and the generated default of api.line.me is used as-is. For lower-level operations, the generated builders are directly accessible via Api.

Design note (the intent behind the asymmetry with Messaging): LIFF is a small closed surface of 2 paths and 4 operations, so convenience methods can cover it completely. Messaging has many endpoints where complete coverage is impractical, so it exposes the generated builders directly. This difference is not an inconsistency but a decision scaled to the size of the surface.

Usage: var liff = LiffClient.CreateWithStaticToken("CHANNEL_ACCESS_TOKEN"); var apps = await liff.GetAppsAsync(); var added = await liff.AddAppAsync(new AddLiffAppRequest { /* ... / }); await liff.UpdateAppAsync(added!.LiffId!, new UpdateLiffAppRequest { / ... */ }); await liff.DeleteAppAsync(added.LiffId!);