This documentation describes the URL parameters that can be used to configure the VQL application.
The application can be configured using URL parameters passed via hash (#) or query string (?). Hash parameters take precedence.
| Parameter | Description | Example |
|---|---|---|
p |
Use for special modes or connecting to a port on localhost.
|
#p=3000 |
s, url |
Use to provide a full URL to a VQL server endpoint. | #s=https://my-vql-server.com/VQL |
ep |
Custom endpoint path appended to the base URL.
|
#ep=/api/vql |
h |
Base64-encoded JSON object for custom HTTP headers. The value must be a base64-encoded JSON string. | #h=eyJhdXRob3JpemF0aW9uIjogIkJlYXJlciB0b2tlbiJ9 |
b |
Base64-encoded JSON object for the request body. The value must be a base64-encoded JSON string. | #h=eyJ0b2tlbiI6ICJhYmMxMjMifQ== |
ml |
Comma-separated list of adapter logic IDs. When provided, the application uses these adapters instead of fetching them from the server. Useful for testing with mock or custom adapter configurations. | #ml=buildings,roads,utilities |
p=web)Web channel mode enables communication between the VQL client and a VQL server running in a different browser tab. This is primarily used for development to connect the UI to a local test server without cross-origin (CORS) issues.
To use this mode, you must have the server environment running on the server.html page in a separate tab.
$host/#p=3000
$host/#s=https://my-vql-server.com
$host/server.html
$host/#p=web
$host/#s=http://localhost:8080&ep=/api/vql
$host/#h=eyJhdXRob3JpemF0aW9uIjogIkJlYXJlciB0b2tlbiJ9
$host/#b=eyJ0b2tlbiI6ICJhYmMxMjMifQ==
$host/#ml=buildings,roads,utilities
$host/#s=http://localhost:8080&ep=/VQL&h=eyJhdXRob3JpemF0aW9uIjogIkJlYXJlciB0b2tlbiJ9&ml=buildings,roads