hyScore.io eases access to contextual and ambient data for anyone by eliminating major obstacles and costs. The customer gets direct access, saves a huge amount of time/resources to get access to this specific data so that they’re able to instantly enhance, develop and create their application, services or other ideas around or based on hyScore’s contextual data.
This documentation is for the hyScore.io contextual API in version 3.
API Release v3 (26th March 2018)
- New: API endpoint https://api.hyscore.io/v3/url for website analysis
- Improvement: algorithm optimization for better results.
- Improvement: new structured JSON response.
- Improvement: enhanced customData parameter into a key/value store.
- Improvement: the image will be always requested
- Improvement: invented message in a new structured JSON response format
- Improvement: besides the metaKeywords, we provide the website description too.
- Feature: provide article headlines in JSON result incl. and in descending order.
Update v3 (20th April 2018)
- New: API endpoint https://api.hyscore.io/v3/text for website analysis
- Improvement: algorithm optimization for better results.
More information available at https://hyscore.io .
INTRODUCTION
No matter if you want to integrate our Contextual Data API into your website with JavaScript or call it from your backend systems written in Java, C#, Python, or any other language. Our Contextual Data API is platform and programming language independent and can be integrated into any system in just a few minutes. It's as simple as sending us an HTTP POST request and receiving the data in JSON format.
How can I get an API-Key?
Just sign-up for our hyScore|cockpit and a personal API-Key will be created automatically. As an alternative, you can write us an email to contact@hyscore.io. We offer 1.000 API requests per month for free so that you can test our service without any costs or risks.
Use cases
Most of our customers use cases can be divided into two different scenarios: real-time and bulk processing. For both the integration is exactly the same, what differs is how the data is "collected" and used.
An example of a real-time scenario is a contextual video player (you can see this example on our website at https://hyscore.io/use-cases/contextual-video ). With just a few lines of JavaScript on your website, you call our API and use the returned contextual data to get the right content into your video player.
Wanting to categorize and catalog your website inventory, is an example of batch processing. You might send us several thousand or even millions of URLs. As this will take some time to process and analyze, let's say you "come back" 15 minutes later to pick up the results. The nice thing is that picking up the results is just sending us the same request again. This keeps the implementation effort for the integration very low.
Comments
0 comments
Article is closed for comments.