EdgeDB can expose an HTTP endpoint for EdgeQL queries. Since HTTP is a stateless protocol, no DDL, transaction commands, can be executed using this endpoint. Only one query per request can be executed.
In order to set up HTTP access to the database add the following to the schema:
using extension edgeql_http;
Then create a new migration and apply it using edgedb migration create and edgedb migrate, respectively.
Your instance can now receive EdgeQL queries over HTTP at
Here’s how to determine your local EdgeDB instance’s HTTP server URL:
hostname will be
port by running
edgedb instance list. This will print a
table of all EdgeDB instances on your machine, including their associated
In most cases,
database_name will be
edgedb. An EdgeDB instance
can contain multiple databases. On initialization, a default database
edgedb is created; all queries are executed against this
database unless otherwise specified.
To determine the URL of a remote instance you have linked with the CLI, you
can get both the hostname and port of the instance from the “Port” column
edgedb instance list table (formatted as
The same guidance on local database names applies here.