Spideo is a SaaS product that specializes in building unique user experiences and personalization through semantic algorithms in easy-to-use discovery tools. We help content providers by providing valuable customer insights to better understand their users and optimize the performance of their content catalog.
The Spideo API has its architecture based on an Application Programming Interface (API). This specifies a set of operations, inputs, outputs, and underlying types that allows you to understand how to integrate our personalized recommendation platform to orchestrate your OTT, VoD and Linear TV platform. Spideo API endpoints provide the building blocks that you need to build your product based on Rest APIs.
Most Spideo API endpoints can be tested with test/dynamic data through our API doc that is exposed here. This lets you see what each API endpoint does. Access to a demo environment will require you to contact our commercial team. Please contact firstname.lastname@example.org to request additional access.
Your username and password obtained during signup to the Spideo API Portal should be used to get access to the Spideo API documentation:
The Spideo API Terms of Service are available at: https://developers.spideo.tv/terms-and-conditions/
Each resource within a REST API can support one or more of the standard HTTP methods. We define which verbs should be supported for each resource (GET, PUT, and DELETE) and their implementation. For example, a GET to the content resource should return a list of content.
The main HTTP responses will be:
In order to keep you in charge of each dummy user that you want to create while performing an API call, which requests you to create a user profile and understand its interaction, we recommend you to follow the following process: Create a user name using the three initials of your company followed by three numbers. For instance, if you work for Spideo then you could choose to create a user called spi100 and respectively spi101, spi102, and so on.
We use a variety of security systems to safeguard the information we maintain and provide. Find out more in our Terms of Service. Our Spideo API supports throttling settings for each method in your API endpoints. You set a standard rate limit and a burst rate limit per second for each method in our REST APIs. Also we monitor the usage by third-party developers, and we provide a stronger mechanism for authorization.
In order to safeguard the information we maintain and provide we use IP whitelisting and Api Key authentication
Our API Doc consists out of different categories in which you can find endpoints that match the specific features of each section. These are:
No, you cannot. Our Spideo API is a closed source.
Yes, this document will be updated from time to time. We maintain a new feature and deprecation feed in our Spideo API Doc.
Get in touch with our commercial team and they will contact you. email@example.com
All our services are served via Restful API. We deploy the technical environment for our customers
on cloud services using AWS or “on-premises”.
This process will depend on the type of service architecture of your IPTV/OTT/Content platform. Most of our partners have chosen to use our Spideo cloud services, as AWS cloud servers offer reliability and scalability.