Query database with SELECT (REST API)
Changed onQuery your database using a simple REST API - no SQL required!
Authentication: Requires auth user access token (from signup/signin)
Row-Level Security: Automatically enforced - you see only data you have access to
Use Cases:
- Query from browser/mobile apps
- Simple data retrieval
- Filtered searches with sorting and pagination
Note: For complex queries (JOINs, CTEs), use a function with direct SQL
Branch-targeted. Runs against the named branch instead of the parent database, using the branch's own credentials. The branch must be active and unexpired. Nothing about this request can reach the parent's data.
Request
- Base URL: https://api.volcano.dev
- URL: https://api.volcano.dev/databases/{databaseName}/branches/{branchName}/query/select
- Auth: HTTP bearer
Path parameters
Database name (unique within project, lowercase letters, numbers, and underscores only)
Branch name (unique within the parent database, lowercase letters, numbers, and underscores only)
Request body
Example request
{
"table": "posts",
"select": [
"id",
"title",
"content",
"created_at"
],
"filters": [
{
"column": "status",
"operator": "eq",
"value": "published"
},
{
"column": "views",
"operator": "gt",
"value": 100
}
],
"order": [
{
"column": "created_at",
"ascending": false
}
],
"limit": 10
}Response
Query successful
Changes
- ▲
added the new path request parameter
branchName - ▲
added the new path request parameter
databaseName - ▲
added the new required request property
- ▲
the request's body type changed from no type to
object - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ▲
the response's body type changed from no type to
objectfor status - ○
added the new optional request property
- ○
added the new optional request property
- ○
added the new optional request property
- ○
added the new optional request property
- ○
added the new optional request property
- ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the optional property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status - ○
added the required property
to the response with the status
- ▲
- ○
added the non-success response with the status
- ○