# Remove an ASO keyword

Remove one tracked keyword from an ASO app.

## Endpoint: DELETE /v1/aso/apps/{appId}/keywords/{keywordId}

- Method: `DELETE`
- Path: `/v1/aso/apps/{appId}/keywords/{keywordId}`
- Authentication: Bearer API credential or OAuth access token
- Required scope: `content:write`
- MCP tool: `manage_aso`
- MCP action: `remove_keyword`

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `appId` | path | uuid | yes | Tracked ASO app id. |
| `keywordId` | path | uuid | yes | Tracked keyword id. |

## Known errors

- 400 invalid_request for an invalid filter, identity or limit.
- 401 authentication_required for a missing or invalid credential.
- 402 subscription_required when access is not entitled.
- 403 authorization_required for a missing scope or unavailable preview access.
- 403 workspace_not_accessible when x-genviral-tenancy names a workspace the credential cannot reach.
- 404 not_found when the record is outside the accessible catalogue.
- 429 rate_limited; honor Retry-After when present.
- 429 daily_call_limit; the plan's daily API and MCP calls are used until 00:00 UTC.
- 409 conflict when the write would duplicate an exclusive row.

## Request

Removes one tracked keyword. This write does not call Apple.

```
curl --request DELETE 'https://api.peekpanda.com/v1/aso/apps/11111111-1111-4111-8111-111111111111/keywords/22222222-2222-4222-8222-222222222222' \
  --header "Authorization: Bearer $PEEKPANDA_TOKEN" \
  --header 'x-genviral-tenancy: personal'
```

## MCP request

Call manage_aso with action remove_keyword. Path fields go in params, filters in query, and a write body in body.

```
{
  "name": "manage_aso",
  "arguments": {
    "request": {
      "action": "remove_keyword",
      "params": {
        "appId": "<appId>",
        "keywordId": "<keywordId>"
      }
    }
  }
}

```

## Response

Empty JSON object. The public Nest handler returns an empty 200.

```
{}

```

## Source

Dated public App Store search results and suggestion observations for the US English storefront. Positions are observed result order. Difficulty and demand are directional indicators, not search volume or advertising data.

## Refresh

Stored observations are reused while current. Explicit refresh commands run asynchronously and report freshness, progress and any applicable limits.