> Source: [sk1000100](https://support.checkpoint.com/results/sk/sk1000100)

# sk1000100 - Network feed creation fails when using a custom header with the Check Point Terraform or OpenTofu provider

| Property | Value |
|----------|-------|
| Solution ID | sk1000100 |
| Date Created | 2026-09-02 |
| Last Modified | 2026-09-08 |
| Technical Level | Advanced |
| Products | Security Management Server |
| Versions | R82, R81.20 |
| OS | Gaia |
| Platform | Smart-1, Azure |

## Symptoms

- * Creating a new `checkpoint_management_network_feed` resource that includes a **custom_header** block fails during the initial `add-network-feed` Management Application Programming Interface (API) call.  
* Terraform or OpenTofu returns:
  * `400 Bad Request`
  * `generic_err_invalid_parameter_name`
* The error message states that the parameter **customHeader** is not recognized.
* The issue occurs with the `CheckPointSW/checkpoint` provider when it uses the Management API `add-network-feed` and `set-network-feed` functionality.
* The same **custom_header** configuration succeeds when updating an existing network feed with `set-network-feed`.  
* The failure is specific to the creation of network feed objects. It is not caused by the custom header values.
* Management API logs in `api.elg` shows a similar error: `UnrecognizedPropertyException: Unrecognized field "customHeader" in NetworkFeedRequestNew`
* A minimal `checkpoint_management_network_feed` configuration with `custom_header` reproduces the same error, for example:

```text
Status: 400 Bad Request
Code: generic_err_invalid_parameter_name
Message: Unrecognized parameter [customHeader]
```

## Cause

An issue in the *CheckPointSW/checkpoint* *Terraform/OpenTofu* provider causes network feed creation requests to use an incorrect Management API parameter name.

During `add-network-feed` operations, the provider sends:`customHeader`

The Management API expects:

`custom-header`

Because `customHeader` is not the correct parameter for the `add-network-feed` command, the Management API rejects the request and returns:

```
generic_err_invalid_parameter_name
Unrecognized parameter [customHeader]
```

The issue affects only network feed creation. Updates to existing network feeds are not affected because the provider uses the correct parameter format during `set-network-feed` operations.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content