Hudu Asset API

Thank you for reaching out!

I have created a demonstration video and attached it to this message. To help guide you through the process, I’ve also provided an example JSON body and cURL request URL below similar to what you are using. I’ll explain each part to ensure you can successfully create assets using the API.

Understanding the JSON Body and API Request
Field Labels in JSON Body:
The labels inside your JSON body (e.g., "LISTFIELD", "ASSETTAG1", etc.) directly map to the field names in your Asset Layout in Hudu.
Ensure that the names used in the JSON body match exactly with the field names in your Asset Layout to avoid errors.
Best Practice for Field Formatting:
The easiest way to understand how fields should be formatted is to:
Manually create an asset in Hudu using your desired Asset Layout.
Run a GET request using the /assets endpoint with the asset’s name as your query.
This GET request will return the asset’s data in the correct format, showing you how each field appears in the API response. You can then use this as a template for future POST requests.

Example cURL Request:
curl -X POST "https://clientsupport.hudu.technology/api/v1/companies/9/assets" \
-H "accept: application/json" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{...}'
Replace the following in the URL:
clientsupport.hudu.technology → with your Hudu domain.
9 → with your specific company ID.
YOUR_API_KEY → with your Hudu API key.

Example JSON Body:
{
  "asset": {
    "name": "Test112",                    // The name of the asset
    "asset_layout_id": 51,                // ID of the Asset Layout used
    "primary_serial": "SN123456789",      // Primary serial number of the asset
    "primary_mail": "[email protected]",   // Primary email linked to the asset
    "primary_model": "Model X",           // Model information
    "primary_manufacturer": "Example Manufacturer", // Manufacturer details
    "slug": "adf496e0ae9c",               // Unique identifier for the asset
    "custom_fields": [
      {
        "LISTFIELD": "{\"list_ids\":[21]}",  // List selection field
        "ASSETTAG1": "[{\"id\":3030,\"url\":\"/a/ddc9e99ac957\",\"name\":\"AA10000234343436\"}]", // asset tag field
        "ASSETTAG2": "[{\"id\":2812,\"url\":\"/a/d9207275c8dd\",\"name\":\"Import testing #2\"}]", // asset tag field
        "ASSETTAG3": "[{\"id\":2810,\"url\":\"/a/0c85302316cf\",\"name\":\"Example Asset\"}]",   // asset tag field
        "MODEL": "more text here, this is a text field",    // Standard text field
        "SERVICETAG": "more text here, this is a text field", // Standard text field
        "DATEFIELD": "2025-02-21T00:00:00.000Z",            // Date field (ISO 8601 format)
        "RICHTEXTFIELD": "<p>This is a rich text field</p>" // Rich text field with HTML formatting
      }
    ]
  }
}
Explanation of Each JSON Field:
Field	Purpose
name	Name of the asset.
asset_layout_id	The ID of the Asset Layout you’re using.
primary_serial	The primary serial number of the asset.
primary_mail	Associated email address.
primary_model	The model of the asset.
primary_manufacturer	The manufacturer of the asset.
slug	Unique identifier for the asset in Hudu.
custom_fields	Holds all additional fields specific to your Asset Layout.
LISTFIELD	Example of a list selection (with list IDs).- This is a field name(a label)
ASSETTAG1/2/3	Links to other assets within Hudu.- This is a field name(a label)
MODEL	Free-text field for the model.- This is a field name(a label)
SERVICETAG	Service tag of the asset.- This is a field name(a label)
DATEFIELD	Date field, formatted as YYYY-MM-DDTHH:MM:SS.ZZZZ.- This is a field name(a label)
RICHTEXTFIELD	Rich text field that supports HTML tags for formatting.- This is a field name(a label)

Key Reminders:
Asset Layout ID: Ensure the asset_layout_id matches the layout you're using.
Field Labels: Match the labels exactly with your Hudu Asset Layout fields.
Custom Fields Formatting: The format for each field depends on its type (e.g., text, list, asset tag, etc.).
API Key: Keep your API key secure and include it in your headers when making API calls.