Manage Allow and Block Lists

Control send/receive/reply policies with global, inbox, and pod-scoped list routes.

View as Markdown

List model

List entries are managed by direction and type:

  • direction: send, receive, reply
  • type: allow, block

Each entry is typically an email value (for example, spam@example.com).

Global lists

Use global list routes to apply policy at tenant scope:

  • GET /agent/v0/lists/{direction}/{type}
  • POST /agent/v0/lists/{direction}/{type}
  • GET /agent/v0/lists/{direction}/{type}/{entry}
  • DELETE /agent/v0/lists/{direction}/{type}/{entry}
curl -X POST https://api.agentry.to/agent/v0/lists/receive/block \
  -H "Authorization: Bearer ag_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"entry":"spam@example.com"}'

Inbox-scoped routes

Inbox list routes use the same list model, but require inbox ownership checks:

  • GET /agent/v0/inboxes/{inbox_id}/lists/{direction}/{type}
  • POST /agent/v0/inboxes/{inbox_id}/lists/{direction}/{type}
  • GET /agent/v0/inboxes/{inbox_id}/lists/{direction}/{type}/{entry}
  • DELETE /agent/v0/inboxes/{inbox_id}/lists/{direction}/{type}/{entry}

Pod-scoped routes

Pod list routes mirror the same flow with pod ownership checks:

  • GET /agent/v0/pods/{pod_id}/lists/{direction}/{type}
  • POST /agent/v0/pods/{pod_id}/lists/{direction}/{type}
  • GET /agent/v0/pods/{pod_id}/lists/{direction}/{type}/{entry}
  • DELETE /agent/v0/pods/{pod_id}/lists/{direction}/{type}/{entry}

Pagination

List endpoints support:

  • limit
  • page_token

Responses return next_page_token when more entries are available.