DocsDeveloper reference

Environments & app data

Every project's sandbox, development, and production environments — and your deployed app's own data.

List environments

A project's environments and their modes. In the CLI, environments are addressed implicitly — every command takes --env <environmentId> or --mode sandbox|development|production.

query Environments($input: EnvironmentsConnectionInput!) {
  environments(input: $input) {
    nodes { id name mode isDefault }
  }
}
# variables
{ "input": { "filters": { "projectId": "prj_..." } } }

Check provisioned infrastructure

Whether an environment's infrastructure is live, its hosting URL, and any failure reason.

query($input: EnvironmentDeployInput!) {
  environmentInfrastructure(input: $input) {
    status deploySlug hostingUrl failureReason
  }
}

Query your deployed app's data

The API reads your deployed app's operational surface — database schema and migrations, error logs, uploaded files, app users, jobs, and analytics. These are API-first operations; reach them from the SDK through the GraphQL escape hatch.

query($input: EnvironmentErrorLogsInput!) {
  environmentErrorLogs(input: $input) { entries }
}
# Related queries, same pattern:
#   environmentSqlSchema, environmentSqlMigrations,
#   environmentUploads, environmentAppUsers,
#   environmentJobs, environmentJobRuns, environmentAnalytics

Databases on Spaceboy

Check and refresh the kernel

Every project vendors the platform kernel. Compare a project's vendored kernel against the current one, and hand the upgrade to an agent task.

spaceboy kernel status prj_...
spaceboy kernel refresh prj_...