# Kinow APIs

# GraphQL API

It is a powerfull API which can be integrated directly inside a front-end application, without server-side rendering or processing.

Indeed, the calls made to the API are authenticated with a user context. It means that the resources available are automaticaly filtered based on the user access rights.

This API can handle huge workload and doesn't have any rate limitation.

The GraphQL API endpoint is public.

Take a look to our Introduction guide.

# Server API

This API works with Rest/JSON and give you an administrator access to your platform, so you can retrieve, create, update or delete all the data.

This API is for a server-side usage and cannot be integrated directly inside a front-end application as it has full access and observes a rate limitation with a maximum number of requests allowed.

The Server API endpoint is private.

Take a look to our Introduction guide.

# Which API to use?

If you are working on a front-end application and do not want to handle the server mechanisms (data synchronization, customer authentication, access rights, etc), use the GraphQL API.

If you already have your own CMS and want to store the data into a server-side database or if you want to do batch operations, you have to use the Server API.

# Webhooks

Listen for events on your Kinow platform to trigger some actions within your integration.

Kinow uses webhooks to notify your application when an event happens through your platform. Webhooks are particularly useful for asynchronous events like when a customer subscribe to your offers or when a video is viewed.

Webhooks usually works with the Server API integration, for example to refresh a server-side database or cache.

Take a look to the list of notifications you can handle inside Webhooks.