My InterServer API
GET /mail/{id}/rules
Api key auth Session id header auth Session id cookie auth

The deny rules allow you to setup assorted types of rules which will automatically deny the email from being sent through our system when the citeria match.

Returns a listing of all the deny block rules you have configured.

Path parameters

  • id integer Required

    Mail ID number

Responses

  • 200 application/json

    OK

    Hide response attributes Show response attributes object

    The data for a email deny rule record.

    • id integer Required

      The deny rule Id number.

    • created string(date-time) Required

      the date the rule was created.

    • user string

      Mail account username that will be tied to this rule. If not specified the first active mail order will be used.

    • type string Required

      The type of deny rule.

      Values are domain, email, startswith, or destination.

    • data string Required

      The content of the rule. If a domain type rule then an example would be google.com. For a begins with type an example would be msgid-. For the email typer an example would be user@server.com.
  • 401 application/json

    Unauthorized

    Hide response attributes Show response attributes object
    • code string Required
    • message string Required
  • 404 application/json

    Unauthorized

    Hide response attributes Show response attributes object
    • code string Required
    • message string Required
GET /mail/{id}/rules 
curl \
 --request GET 'https://my.interserver.net/apiv2/mail/{id}/rules' \
 --header "X-API-KEY: $API_KEY"
Response examples (200) 
[
  {
    "id": 14,
    "data": "domeinwo@server.guesshost.net",
    "type": "email",
    "user": "mb20682",
    "created": "2022-03-22 19:16:35"
  },
  {
    "id": 15,
    "data": "mamediieva@thedigital.gov.ua",
    "type": "email",
    "user": "mb20682",
    "created": "2022-03-22 19:18:01"
  }
]
Response examples (401) 
{
  "code": "string",
  "message": "string"
}
Response examples (404) 
{
  "code": "string",
  "message": "string"
}