---
title: "What the builder decided about this repo"
method: GET
path: "/client/services/{id}/build"
tags: ["Apps"]
---

# What the builder decided about this repo

`GET /client/services/{id}/build`

## Request

- Base URL: `https://api.roar-ai.com`
- URL: `https://api.roar-ai.com/client/services/{id}/build`
- Auth: HTTP bearer

The framework it detected, the commands it will run, and the root directory it resolved. **Read this before theorising about a failed deploy** — it says which branch the builder took.

`envKeys` is what your repo's committed `.env.example` asks for, read from your app's ROOT DIRECTORY (so a monorepo app in `app/` is read from `app/.env.example`). `missingEnv` is the subset nothing has set — the actionable half, and the usual reason a build succeeds and the container then fails. Both are null until a deploy has recorded one; `[]` means the repo committed no example file, which is a different answer. `id` is a SERVICE id — take it from `services[].id` on `GET /client/apps/{appId}`, not the app id itself.

## Path parameters

- `id` string, uuid, required

## Response `200`

Build settings and detection

## Other responses

- `404`: No such app service

---

[API](https://skmtc.dev/roar-ai/apis/roar-ai-api.md) · [All operations](https://skmtc.dev/roar-ai/apis/roar-ai-api/llms.txt) · [OpenAPI document](https://skmtc.dev/roar-ai/apis/roar-ai-api/revisions/37e4d0d5a7fe?raw)