---
title: "POST /detector/{detectorId}/member/stop"
method: POST
path: "/detector/{detectorId}/member/stop"
---

# POST /detector/{detectorId}/member/stop

`POST /detector/{detectorId}/member/stop`

Stops GuardDuty monitoring for the specified member accounts. Use the `StartMonitoringMembers` operation to restart monitoring for those accounts.

With `autoEnableOrganizationMembers` configuration for your organization set to `ALL`, you'll receive an error if you attempt to stop monitoring the member accounts in your organization.

## Path parameters

- `detectorId` string, required

## Request body

- object
  - `accountIds` AccountId[], required — A list of account IDs for the member accounts to stop monitoring.

## Response `200`

Success

- StopMonitoringMembersResponse
  - `UnprocessedAccounts` UnprocessedAccount[], required — A list of objects that contain an accountId for each account that could not be processed, and a result string that indicates why the account was not processed.
    - `AccountId` string, required — The Amazon Web Services account ID.
    - `Result` string, required — A reason why the account hasn't been processed.

## Other responses

- `480` — BadRequestException
- `481` — InternalServerErrorException

---

[API](https://skmtc.net/aws/apis/guardduty.md) · [All operations](https://skmtc.net/aws/apis/guardduty/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/aws/guardduty/versions/d35ef49b25a3/schema)