Finds the most specific record defined for the given search key, date, and time.
Request a record with scope at specific level using
GET {+table}/data/idKey/exact
Path Elements
+table
string
|
The URI path to a specific table (whether
by ID or
by name).
|
Matrix Parameters
;columnName=...
appended to data
string
|
Used when only a subset of the existing column values in the record is desired.
By specifying specific column names, the requested record is filtered to only
contain the specified columns.
When no column names are specified, all existing columns are returned.
The text columnName is a placeholder and must be replaced with
an exact column name from the table. Repeat as necessary for any
additional columns desired, in any order.
The value of the matrix parameter is reserved for future use and should not be specified.
example values
;Competitor%20Price=
;Base%20Price
;Competitor%20Price;Base%20Price;AveragePrice
|
;searchDimensionID=...
appended to idKey
string
|
The scope specifies the dimensionality of where the record
should be found and is made up of an unordered list of
dimension - dimension node pairs, where each dimension can only appear once.
When associated with the idKey it is required that in the scope
both dimensions and dimension nodes are specified by IDs.
The scope will used to find a record by walking the access sequence of the
table and returning the first matching record encountered.
The dimension ID is placed on the left side of the equals sign of the matrix parameter
and the dimension node ID is placed on the right side.
example values
;c689acc7-ee13-3482-aa7b-c6a13419431c=7baaa4ab-dd43-31a2-9454-ebc60fb910d5
;c689acc7-ee13-3482-aa7b-c6a13419431c=7baaa4ab-dd43-31a2-9454-ebc60fb910d5;28484058-4ffc-329b-94ff-63e1ddbd7189=27de4ae8-61be-3fff-a397-16362cafeba2
|
Query Parameters
on
string
|
The date-time without a time-zone in the ISO-8601 calendar system that is used to resolve
the value, such as 2014-12-03T10:15:30. The precision is to the Second.
Nanosecond field is ignored. The time fields are optional. If time is not specified, it
is default to 00:00:00. If this parameter is not specified, the server time at which this
request is processed is used.
example values
2014-12-03T10:15:30
2014-12-03T10:15
2014-12-03
|
Example
- Request Data Using IDs in Scope
Request:
Response:
HTTP/1.1
200
OK
{
"tableID" : "bb18498a-3228-425a-816c-481bac1030ca",
"start": "2014-04-14T10:05:43",
"end": "2014-05-18T20:14:21",
"key": [
{
"dimID" : "28484058-4ffc-329b-94ff-63e1ddbd7189",
"dimName" : "SAMPLE_PRODUCTS",
"nodeID" : "27de4ae8-61be-3fff-a397-16362cafeba2",
"nodeName" : "0011491975135"
},
{
"dimID" : "c689acc7-ee13-3482-aa7b-c6a13419431c",
"dimName" : "LARGE_CITIES",
"nodeID" : "7baaa4ab-dd43-31a2-9454-ebc60fb910d5",
"nodeName" : "US-TX"
}
],
"values" : [
{
"name" : "Forecasted Volume",
"value" : "17.26172",
"unit" : "cubic feet",
"perQuantity" : 1
},
{
"name" : "Product Cost",
"value" : "7.97181",
"unit" : "Each",
"currency" : "DKR",
"perQuantity" : 1
}
]
}
Error
Example
- Request Data Using IDs in Scope, Multiple Nodes Specified for One Dimension
Request:
Response:
HTTP/1.1
400
BAD REQUEST
{
"errorID" : "HVS-004021",
"errorMessage": "Expected one node identifier per key dimension, found: 2.",
"resourceType": "record",
"requestID" : "d0af9f1b-3159-4212-940e-ce984c19e8d3"
}
Error
Example
- Request Data Using IDs in Scope, Multiple Nodes Specified for One Dimension
Request:
Response:
HTTP/1.1
400
BAD REQUEST
{
"errorID" : "HVS-004025",
"errorMessage": "Required dimension node value for dimension 28484058-4ffc-329b-94ff-63e1ddbd7189 was not set.",
"resourceType": "record",
"requestID" : "d0af9f1b-3159-4212-940e-ce984c19e8d3"
}