Add Properties

In this case, the adapter instance used for pushing data will default to SuiteAPI. It is recommended (though not required) to use this API when the resource was created using the API
POST /api/resources/{id}/adapters/{adapterInstanceId}. Otherwise an additional adapter instance might be created.
Note: Those properties that are specified with old timestamp will be published with current time. As a result, only one of those properties will appear in vROps (e.g. the latest one will overwrite all previous ones).

Request

URI

POST

https://{api_host}/suite-api/api/resources/{id}/properties

COPY

Path Parameters

string

Required

The ID of the resource

Request Body

The properties for the Resource

property-contents of type(s) application/json

Required

Show optional properties

{
    "property-content": [
        {
            "statKey": "string",
            "timestamps": [
                {}
            ]
        }
    ]
}

"{\n  \"property-content\" : [ {\n    \"statKey\" : \"system|availability\",\n    \"timestamps\" : [ 1119844280663 ],\n    \"values\" : [ \"UP\" ]\n  }, {\n    \"statKey\" : \"config|num|processes\",\n    \"timestamps\" : [ 1119844280663 ],\n    \"data\" : [ 93.0 ]\n  } ]\n}"

array of object

property-content

Required

Collection of property contents

Authentication

This operation uses the following authentication methods.

Token-based-authorization

Responses

200

The properties are added successfully

Operation doesn't return any data structure

Code Samples

COPY

                    curl -X POST -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '{"property-content":["object"]}' https://{api_host}/suite-api/api/resources/{id}/properties

On This Page

Description

Request

Path Parameters

Request Body

Authentication

Response

200 Response Body

Resource Operations

GET

Get Relationship

PUT