To create a new resource in the Cisco FDM API, a POST request is sent to the collection endpoint. The endpoint for network-related objects (including hosts, ranges, and subnets) is /object/networks. Within the JSON payload, the "type" attribute for these entities must be defined as "networkobject", while the specific nature of the object (Host) is defined by the subType. For authentication, Cisco FDM utilizes token-based security, requiring the "Bearer" prefix in the Authorization header. The option f'{BASE_URL}/object/hosts/{ID}' is incorrect for creation as it is a specific resource URI used for GET, PUT, or DELETE operations on an existing object ID.

Cisco DevNet: Firepower Device Manager REST API Guide. Section: "Working with Network Objects."

Details: Specifies the POST method to /object/networks for creating new host objects.

Cisco Firepower Threat Defense (FTD) API Explorer (Built-in Documentation). Endpoint: POST /object/networks.

Details: Defines the schema where 'type' must be 'networkobject' and 'subType' can be 'HOST', 'NETWORK', or 'RANGE'.

Cisco FDM API Authentication Overview. Section: "Token-Based Authentication."

Details: Confirms the use of HTTP Authorization header with the 'Bearer' scheme for API calls following the initial login.

RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token Usage.

Details: Standardizes the Authorization: Bearer format used by modern REST APIs like Cisco FDM.