Sioslife is a company that develops innovative technology solutions that help overcome the challenges of the best age through user-friendly interactive platforms.
The elderly population and technology were two distant realities that could be brought together. When noticing this problem that exponentiated senior loneliness and lack of social activity, we realized that everyday challenges could be solved through adaptable and innovative solutions.
Our interactive systems suit each user. A clear system that gives freedom to the senior and a peace of mind that only this can give. An accessible and present system, just like the Sioslife team. A system that eliminates borders, and that enhances the re-creation of a community united by technology. All in one!
Because we believe in an inclusive world for the elderly, Sioslife creates technological solutions that contribute to a more active and happier aging.
Sioslife Integration Layer is a REST API system that powers our platform for interactions between seniors and caregivers. In this API is a software layer connecting and optimizing communications between our own applications, external services and various partners.
API is short for 'Application Programming Interfaces'. An API is a set of rules that lets programs talk to each other, exposing data and functionality across the Internet in a consistent format.
REST stands for 'Representational State Transfer'. This is an architectural pattern that describes how distributed systems can expose a consistent interface. When people use the term 'REST API', they are generally referring to an API accessed using the HTTP protocol at a predefined set of URLs.
These URLs represent various resources — any information or content accessed at that
location, which can be returned as JSON, HTML, audio files, or images. Often resources have
one or more methods that can be performed on them over HTTP, like GET,
POST, PUT, PATCH and DELETE. How they
are defined is confusing, but the general rule is:
GET to obtain a list of resources or a single resourcePOST to create resourcesPUT to update all properties of a single resourcePATCH to update some properties of a list of resources or a single resource
DELETE to delete a list of resources or a single resourceMaybe you are looking for our company's page at Sioslife.com
If you need any help you can contact us by sending us an e-mail to development@sioslife.com. We are here to help you helping us improving our seniors's life.
Authentication is when an entity proves an identity. In other words, Authentication proves that you are who you say you are. This is like having a driver license which is given by a trusted authority that the requester, such as a police officer, can use as evidence that suggests you are in fact who you say you are.
While there are as many proprietary authentication methods as there are systems which utilize them, they are largely variations of a few major approaches (you can read more about it here). Sioslife Integration Layer uses 2 of them:
Bearer authentication (also called token authentication) is an HTTP authentication scheme that involves security tokens called bearer tokens.
The name "Bearer authentication" can be understood as "give access to the bearer of this token". The bearer token allowing access to a certain resource or URL and most likely is a cryptic string, usually generated by the server in response to a login request.
For the Sioslife Integration Layer, the client must send this token in the "Authorization"
header when making requests to protected resources:
Authorization: Bearer <token>
The Bearer authentication scheme was originally created as part of OAuth 2.0 in RFC-6750 but is sometimes also used on its own.
Similarly to Basic authentication, Bearer authentication should only be used over HTTPS (SSL).
Sioslife Integration Layer uses Bearer authentication to authenticate Users and Devices using the system.
An Application Programming Interface key (API key) is a unique identifier used to authenticate a user, developer, or calling program to an API. However, they are typically used to authenticate a project with the API rather than a human user. Different platforms may implement and use API keys in different ways.
The API key often acts as both a unique identifier and a secret token for authentication, and will generally have a set of access rights on the API associated with it.
For the Sioslife Integration Layer, the client must send this key in a "X-API-KEY" header when
making requests to protected resources:
X-API-KEY: <key>
Sioslife Integration Layer uses API Key authentication to authenticate External services and Partners using the system.
Are you a Sioslife partner that needs an API-key? Contact us by sending us an e-mail to development@sioslife.com.