External API docs

Delete deny rules

Remove previously created deny rules so those emails or phone numbers can appear in enrichment results again.

Overview

Use this endpoint to remove deny rules that you created earlier. Only rules matching the exact (type, value) tuples in the body are removed. Values with no matching rule are silently ignored, so the call is safe to replay.

Before you start

Make sure you have:

  • an Openmart account
  • an API key
  • a tool to send API requests, such as Postman or curl

Authentication: send your key in the X-API-Key header. Authorization: Bearer <key> is also accepted. Deny rules are scoped per-user (per-key), so rules you create only apply to your own enrichment requests.

1

Example: Unblock an email address

Endpoint
DELETE https://api.openmart.ai/api/v2/deny-rules

Parameters

Parameter
type
Type
string (enum)
Required
Yes
Example
"email"
Description
Identifier kind. Must be exactly "email" or "phone"; any other value returns 400 detail:"Type must be one of [email phone]".
Parameter
values
Type
array[string]
Required
Yes
Example
["blocked@example.com"]
Description
Literal identifiers to add, remove, or check. Emails are matched case-insensitively at lookup time. Phones should be E.164 formatted.

cURL request

cURL
curl --request DELETE \
  --url https://api.openmart.ai/api/v2/deny-rules \
  --header 'Accept: application/json' \
  --header 'X-API-Key: <your_api_key>' \
  --header 'Content-Type: application/json' \
  --data '{
    "type": "email",
    "values": ["blocked@example.com"]
  }'

Response example

JSON
{
  "status": "success"
}

Key elements of the API response

Response element
status
Description
Always "success" on HTTP 200. If a supplied value had no matching rule, it is silently ignored (no partial-failure indicator).

All request parameters

Request body for DELETE /api/v2/deny-rules. Same shape as create and check.

Request body

All three deny-rules endpoints (create, delete, check) share the same body shape.

typestring (enum)Required: Yes
Example: "email"

Identifier kind. Allowed: "email", "phone". Validated via binding:"required,oneof=email phone" — invalid values return HTTP 400 with {"detail":"Type must be one of [email phone]"}.

cURL example
cURL
curl --request POST \
  --url https://api.openmart.ai/api/v2/deny-rules \
  --header 'Accept: application/json' \
  --header 'X-API-Key: <your_api_key>' \
  --header 'Content-Type: application/json' \
  --data '{"type":"email","values":["blocked@example.com"]}'
valuesarray[string]Required: Yes
Example: ["blocked@example.com","spam@example.com"]

One or more literal identifiers. No wildcards. Rules are scoped per-user (via your API key), so another team’s rules do not affect you.

cURL example
cURL
curl --request POST \
  --url https://api.openmart.ai/api/v2/deny-rules \
  --header 'Accept: application/json' \
  --header 'X-API-Key: <your_api_key>' \
  --header 'Content-Type: application/json' \
  --data '{"type":"email","values":["blocked@example.com","spam@example.com"]}'
# Delete Deny Rules

## Endpoint

DELETE https://api.openmart.ai/api/v2/deny-rules

## Description

Remove deny rules that you previously created. Values with no matching
rule are silently ignored — the call is safe to replay.

## Authentication

- `X-API-Key: <your_api_key>` (recommended)
- `Authorization: Bearer <your_api_key>` (also accepted)

## Request body

```json
{
  "type":   "email",
  "values": ["blocked@example.com"]
}
```

Same shape as create and check.

## Example Request

```bash
curl -X DELETE "https://api.openmart.ai/api/v2/deny-rules" \
  -H "Accept: application/json" \
  -H "X-API-Key: <your_api_key>" \
  -H "Content-Type: application/json" \
  -d '{"type": "email", "values": ["blocked@example.com"]}'
```

## Example Response

```json
{
  "status": "success"
}
```

## Errors

- 400 — bad JSON or bad `type` (`{"detail":"..."}`)
- 401 — missing or invalid API key
- 500 — persistence failure