- Print
Report new values for API machine attributes. All attribute IDs must be associated with their respective machines. A value must be congruent with the attribute's associated type. No attributes are processed if any of them fail validation.
Requires the attributes:write
API key scope.
A Tulip API key is required to use the Tulip API. API key authentication uses HTTP Basic Authentication as defined by RFC 7617. HTTP Basic Authentication uses a generic username/password scheme to authenticate. For Tulip API requests, the password should be the API key's associated secret. The username should have the format {type}.{version}_{id}
, where {type}
is the API key type, {version}
is the type's version number, and {id}
is the id of the key. Tulip API keys currently are one of two types:
apikey.2
- user API keys provisioned by creating a Tulip API Token. The key id is the token id.onetime.1
- temporary API keys provisioned using the/auth/temporary
endpoint or using the One-Time API Key page. These keys are only valid for 30 seconds after provisioning.
Once you have determined the username and password you need to use, the Authorization
header should be set to the value Basic {credentials}
, where {credentials}
is the base64-encoded value of the string {username}:{password}
. See RFC 7617 for more details of this encoding.
Attributes to report.
Machine attribute values to report for processing.
Value to submit. The value's type must be congruent with the attribute type. Incorrect typing will generate a 422 response.
Attributes were succesfully reported.
The request was malformed. This could mean that headers, query parameters, or the request body was unable to be parsed or had unexpected values.
The request was syntactically sound, but could not be processed due to a logical problem.
The server encountered an unexpected error.