Remote Config Sources

OBM2 Pro can pull LoliScript configs from one or more remote endpoints. This is a client-side download feature — the app fetches a packaged set of configs over HTTP. It does not run a server, expose the app over an API, or allow remote runner control.

About

A source is a remote URL that returns a ZIP archive of .loli configs. When you pull from your sources, OBM2 Pro downloads the archive, extracts the configs and adds them to the Config Manager under the Remote category. Remote configs are loaded read-only: they live in memory for the session and are not written to your local configs folder.

ℹ

This is the only "remote" capability in OBM2 Pro. Unlike the original OpenBullet, there is no standalone API service, no JWT login, and no remote start/stop of runners — only config retrieval.

Adding a Source

Open Settings → Sources and add one entry per remote endpoint:

Field	Description
API URL	The endpoint that returns the configs archive, e.g. `https://my-server.com/configs`.
Auth mode	`API Key` or `Username / Password`.
API Key	Sent verbatim in the `Authorization` header (API Key mode).
Username / Password	Sent as HTTP Basic auth — `Authorization: Basic base64(user:pass)` (User/Pass mode).

Pulling Configs

From the Config Manager, trigger the pull from sources. For each configured source the app performs a single HTTP request, attaching the authentication header:

# API Key mode
GET <API URL>
Authorization: <your-api-key>

# Username / Password mode
GET <API URL>
Authorization: Basic <base64(username:password)>

The downloaded configs appear under Remote (or Remote - <subfolder> when the archive uses folders). They can be opened and run like local configs, but they cannot be edited or saved over.

Server Response Format

Your endpoint must return a ZIP archive whose entries are LoliScript config files. The folder structure inside the archive is preserved as sub-categories in the Config Manager.

Case	Response
Success	HTTP body = a ZIP archive of `.loli` files.
Error	Response header `Result: Error`, with the body carrying a plain-text error message that the app shows in the log.

⚠

Credentials travel in the Authorization header. Always serve your sources over HTTPS so API keys and passwords are not exposed in transit.