# Allow or decline an action on a connected account

> POST /v1/builds/{build_id}/approvals/{approval_id}

Source: https://docs.fous.com/api-reference/decideBuildAction

`POST /v1/builds/{build_id}/approvals/{approval_id}`

A build that runs with a connected account sends nothing but plain reads to it until a person allows each other request (GET /v1/builds/{build_id} shows it as pending_approval while waiting_for is approval). approve sends it; with scope build, every later request of the same kind in this build is allowed too. decline refuses it: the build goes on without it and never retries it. Show the person the action’s connection, method, URL, body preview and steps, and obtain their explicit decision; never decide for them. An approval nobody answers within 24 hours expires and the build stops. Needs tools:write.

Authentication: `Authorization: Bearer $FOUS_API_KEY`.

## Path parameters

- `build_id` (string, required)
- `approval_id` (string, required)

## Request body

Required. JSON.

- `decision` (string, required): One of "approve", "decline".
- `scope` (string): With approve: this request only, or its kind for the whole build. Default "once". One of "once", "build".

## Response 200

Decided; the build resumes

- `success` (true, required)
- `data` (Build, required): A build: from queued through exploring, compiling, verifying and publishing to ready, failed or cancelled. Once ready, api names the tool and method its operation; prepared_request carries an input the builder verified it with.

## Errors

Every error uses the Error schema: branch on `error.code`. Codes are listed at https://docs.fous.com/guides/errors.

- 400
- 401 (headers: WWW-Authenticate)
- 402
- 403
- 404
- 408
- 409
- 410
- 413
- 422
- 429 (headers: Retry-After)
- 500
- 502
- 503 (headers: Retry-After)
- 504

## Example request

```bash
curl 'https://api.fous.com/v1/builds/{build_id}/approvals/{approval_id}' \
  -X POST \
  -H "Authorization: Bearer $FOUS_API_KEY"
```