wisent-app command
import
Import one canonical Wisent account-data JSON document into the authenticated account.
Usage
wisent-app import <wisent-export.json> [--session-file <file> | --token-stdin] [--api-base <url>]
The command resolves and parses the input file locally, refuses files larger than 10 MiB, then sends the original JSON document to the authenticated account-data import operation.
Authentication and options
Credential input
By default the command reads ~/.config/wisent/session.json, which must contain a Supabase access_token. On macOS and Linux the file must have mode 0600. Use --token-stdin to pipe a bearer token instead. Tokens are never accepted in arguments or environment variables.
Shared options
--session-file <file>- Read a session from this path instead of the default. Also configurable with
WISENT_SESSION_FILE. --token-stdin- Read the bearer token from standard input. It cannot be combined with
--session-file. --api-base <url>- Use a different API base instead of
https://bobloo.com/api. Also configurable withWISENT_API_BASE. HTTPS is required except for localhost.
Result and exit status
A successful response prints the imported, unchanged, conflicting, and rejected totals followed by one status line per record. A wrong invocation (missing or unknown argument, no API address) prints the usage and exits 2. Conflicts and rejections print every record, then "Import incomplete" with their counts, and exit 1; credential, file, transport, or unexpected-response failures also exit 1 with their cause and never print credential contents.
Graphical import and document contract
The web, iOS, and Android import flows use the same document and server operation. Read the account-data guide for the graphical workflow, accepted records, duplicate handling, atomic validation, and explicit refusals.
Related command: wisent-app export.