Historics/prepare endpoint error on web console


#1

The web console (http://console.datasift.com/datasift) “historics/prepare” endpoint returned a response body containing:
“error”: “You do not have access to this feature”

This was step #2 of the historics procedure at http://dev.datasift.com/docs/historics/historics-steps.

I retried the “historics/prepare” request at least two time, with the same result.

Do I need to enable a historics “feature”, or change something else?
I am using a “free” account.

Below, MY_KEY and MY_NAME are my credentials.

I filled in the web form, as shown in the resulting "Call"s below.

The “hash” value was successfully created on the “compile” endpoint from this same web form, where I entered:
interaction.content contains “apple”


compile endpoint
Call

api.datasift.com/compile?csdl=interaction.content%20contains%20"apple"&api_key=MY_KEY&&username=MY_NAME

Response Headers

{
“server”: “nginx/0.8.55”,
“date”: “Mon, 18 Feb 2013 23:31:30 GMT”,
“content-type”: “application/json”,
“transfer-encoding”: “chunked”,
“connection”: “close”,
“p3p”: “CP=“CAO PSA””,
“x-ratelimit-limit”: “10000”,
“x-ratelimit-remaining”: “9995”,
“x-ratelimit-cost”: “5”,
“x-served-by”: “ded2587”
}

Response Body

{
“hash”: “9fe133a7ee1bd2757f1e26bd78342458”,
“created_at”: “2011-05-12 11:18:07”,
“dpu”: “0.1”
}


historics/prepare endpoint
Call

api.datasift.com/historics/prepare?hash=9fe133a7ee1bd2757f1e26bd78342458&start=1329600000&end=1329609392&name=apple&sources=facebook&sample=100&api_key=MY_KEY&&username=MY_NAME

Response Headers

{
“server”: “nginx/0.8.55”,
“date”: “Tue, 19 Feb 2013 03:13:01 GMT”,
“content-type”: “application/json”,
“transfer-encoding”: “chunked”,
“connection”: “close”,
“p3p”: “CP=“CAO PSA””,
“x-ratelimit-limit”: “10000”,
“x-ratelimit-remaining”: “9850”,
“x-ratelimit-cost”: “25”
}

Response Body

{
“error”: “You do not have access to this feature”
}


#2

To be granted access to Historics you will need to be on a monthly subscription. You can get in touch with our sales team to discuss this via our Contact Us form.


#3

Thank you for the information, Jason.