Block Publishers At Account Level

📘

Publisher Networks

• Blocking of publisher networks is not supported via the API. (If do you need to block a publisher network, please reach out to your Taboola Account Manager.)
• Attempting to submit a network id to the block-publisher endpoint results in a 400 Bad Request.

Updating

Examples

1. Apply suppressions:

POST /backstage/api/1.0/demo-advertiser/block-publisher

{
    "sites": [
        "site_1",
        "site_2"
    ]
}

{
    "sites": [
        "site_1",
        "site_2"
    ]
}

📘

When updating a resource, you can use either PUT or POST.

📘

For a successful request, the response is the updated list of suppressed publishers.

📘

Sites

The sites field stores a collection of sites (machine-readable site names - i.e. publisher account_ids). For more information, see: List Of Publishers.

2. Remove all suppressions:

POST /backstage/api/1.0/demo-advertiser/block-publisher

{
    "sites": []
}

{
    "sites": []
}

Patching

You can use the PATCH verb to add/remove specific publishers - without re-submitting the entire collection.

Flow

1. Use the PATCH verb to submit an object with 2 fields to the block-publisher endpoint:
   • sites
   • patch_operation ("ADD" or "REMOVE")
2. In the sites field, include only the sites that you want to add or remove.

Examples

1. Fetch the list of blocked publishers:

GET /backstage/api/1.0/demo-advertiser/block-publisher

{
    "sites": [
        "site_1",
        "site_2"
    ]
}

2. ADD sites to the list of blocked publishers

PATCH /backstage/api/1.0/demo-advertiser/block-publisher

{
   "sites": [
      "site_name3"
   ],
   "patch_operation": "ADD"
}

{
    "sites": [
        "site_name1",
        "site_name2",
        "site_name3"      
    ]
}

3. REMOVE sites from the list of blocked publishers

PATCH /backstage/api/1.0/demo-advertiser/block-publisher

{
    "sites": [
        "site_name1"
    ],
    "patch_operation": "REMOVE"
}

{
    "sites": [
        "site_name2",
        "site_name3"      
    ]
}