Build Log
Fetch a deploy's full build log as plain text — success or failure. The log is captured for every build, so it's the fastest way to see why a deploy reached status = failed or what a successful build ran.
While a build is still running the log grows; poll this endpoint to tail it. The X-Build-Status response header reports the deploy status (queued / processing / ready / failed / superseded) so you know when to stop polling.
Response
Content-Type text/plain
The raw build output (capped at 4 MiB).
X-Build-Status header
The deploy status; stop polling once it is terminal (
ready/failed/superseded).Errors
404
Deploy not found or belongs to another application.
Request
curl -i \
"https://api.ngris.com/v1/applications/019be838-d261-7d9b-9499-71995a3a91c6/deploys/019bfcc3-acae-71e4-a084-e58362ea942d/logs" \
-H "X-API-KEY: <your_api_key>"
Response — 200 OK
X-Build-Status: ready
Content-Type: text/plain; charset=utf-8
$ npm ci
added 214 packages in 6s
$ npm run build
vite v5.2.0 building for production...
✓ 142 modules transformed.
dist/index.html 0.46 kB
✓ built in 3.11s
Was this helpful?