Hardware Asset Mapping

Map hardware assets in Technopedia by using the following endpoints:

  • POST https://data.technopedia.com/mapping/hardware
    Use this endpoint for a single asset request only.

  • POST https://data.technopedia.com/mapping/batch/hardware
    Use this endpoint to make a single or batch request for 1 – 5000 assets.

Mapping a hardware asset

The hardware asset mapping endpoint accepts hardware asset data in a JSON object and maps that data to an entity in Technopedia, which is returned with Technopedia IDs when a match is made.
When the asset is matched in the database, Technopedia IDs are returned for the hardware model and hardware product that are associated with the hardware asset.

To submit a single asset request, the JSON object must be submitted in the body of an HTTP POST request to the /mapping/hardware endpoint.

The following example shows the format that you must use to submit the data in the body of the POST request:
POST https://data.technopedia.com/mapping/hardware

{
      "title": "<value>",
      "model": "<value>",
      "manufacturer": "<value>"
}

Important!

All the fields in the JSON object that are submitted in the POST request must be matched in Technopedia before a Technopedia ID is returned.

Note:

The /mapping/hardware endpoint accepts one JSON object per HTTP POST request.

The following example shows an HTTP POST request in Postman for a JSON object with the title: "Acer Aspire 5516". This data is matched in Technopedia and Technopedia IDs are returned for the Acer Aspire 5516 model and product.
Figure 1. HTTP POST request in Postman

Mapping a single asset example

The following examples show a single asset request to https://data.technopedia.com/mapping/hardware

POST  https://data.technopedia.com/mapping/hardware

Request Body

{
     "title": "Acer Aspire 5516",
     "model": "Aspire 5516",
     "manufacturer": "Acer"
}

RESPONSE

[
    {
        "class": "hardware",
        "technopedia_id": "6c7d3624-00ea-47e7-949b-071656bb7c0e",
        "type": "model"
    },
    {
        "class": "hardware",
        "technopedia_id": "2e896a9b-760b-4e97-885c-f171d24418b8",
        "type": "product"
    }
]
curl -X POST \
  https://data.technopedia.com/mapping/hardware \
  -H 'Authorization: Bearer 3222d6aa-410f-4fb5-9693-32323d5c1c04' \
  -H 'Content-Type: application/json' \
  -H 'Postman-Token: 1c78d20c-a4cd-4ee1-8be8-4b4ff34c52f2' \
  -H 'cache-control: no-cache' \
  -d '{
     "title": "Acer Aspire 5516",
     "model": "Aspire 5516",
     "manufacturer": "Acer"
}

RESPONSE

[
    {
        "class": "hardware",
        "technopedia_id": "6c7d3624-00ea-47e7-949b-071656bb7c0e",
        "type": "model"
    },
    {
        "class": "hardware",
        "technopedia_id": "2e896a9b-760b-4e97-885c-f171d24418b8",
        "type": "product"
    }
]

Take the Technopedia ID that is returned and use the TID Endpoint to get asset data from Technopedia.
GET https://data.technopedia.com/technopedia-id/<technopedia-id>
GET https://data.technopedia.com/technopedia-id/6c7d3624-00ea-47e7-949b-071656bb7c0e

Mapping single or multiple software assets

To submit single or multiple assets in a POST request, the JSON objects must be submitted in the body of an HTTP POST request to the /mapping/batch/hardware endpoint.
The following example shows the format that you must use to submit the data in the body of the POST request:
POST https://data.technopedia.com/mapping/batch/hardware

[
  {
   "title": "<value>",
   "model": "<value>",
   "manufacturer": "<value>"
  },
  {
   "title": "<value>",
   "model": "<value>",
   "manufacturer": "<value>"
  }
]
[
  {
   "title": "<value>",
   "model": "<value>",
   "manufacturer": "<value>"
  }
]

The following example shows an HTTP POST request in Postman for JSON objects that have the titles: "Acer Aspire 5516" and "Acer Aspire 5517".
This data is matched in Technopedia and Technopedia IDs are returned for model and product.
Figure 2. HTTP POST request in Postman

Examples of single and multiple assets requests

POST https://data.technopedia.com/mapping/batch/hardware

Request Body for a single asset request

[
 	{
		"title": "Acer Aspire 5516",
		"model": "Aspire 5516",
		"manufacturer": "Acer"
	}
]


RESPONSE

[
    
        {
            "class": "hardware",
            "technopedia_id": "6c7d3624-00ea-47e7-949b-071656bb7c0e",
            "type": "model"
        },
        {
            "class": "hardware",
            "technopedia_id": "2e896a9b-760b-4e97-885c-f171d24418b8",
            "type": "product"
        }
]
POST https://data.technopedia.com/mapping/batch/hardware

Request Body for multiple assets request

[
 	{
		"title": "Acer Aspire 5516",
		"model": "Aspire 5516",
		"manufacturer": "Acer"
	},

	{
		"title": "Acer Aspire 5517",
		"model": "Aspire 5517",
		"manufacturer": "Acer"
	}
]


RESPONSE

[
    [
        {
            "class": "hardware",
            "technopedia_id": "6c7d3624-00ea-47e7-949b-071656bb7c0e",
            "type": "model"
        },
        {
            "class": "hardware",
            "technopedia_id": "2e896a9b-760b-4e97-885c-f171d24418b8",
            "type": "product"
        }
    ],
    [
        {
            "class": "hardware",
            "technopedia_id": "173e9db3-8087-4f89-bce8-7abde7515a2e",
            "type": "model"
        },
        {
            "class": "hardware",
            "technopedia_id": "2e896a9b-760b-4e97-885c-f171d24418b8",
            "type": "product"
        }
    ]
]

Hardware Asset Mapping


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.