Introduction

Socialboards is a customer interaction platform delivered by Socialboards AS.

Our platform lets collect, respond and analyze customer support tickets across multiple channels, such as social media, email, chat and webforms.

Please note that this documentation might be subject to changes. Some changes will occur to both the webhooks- and API description in the end of 2019, as we are preparing v2 of all our API's. This also includes the structure of the document.

GDPR compliance

As Socialboards is a customer support tool, our data contains personal information which is subject to the General Data Protection Regulation (GDPR).

When you use our APIs and Webhooks, our business terms require that you have an appropriate legal basis to collect and process User information. Under GDPR and other EU data protection regulations, you are required to obtain end User consent before sending data via our platform. Thus, you need to ensure that your implementation meets these consent requirements.

What this documentation covers

This documentation targets developers who want to communicate programmatically with the Socialboards platform. You'll find all the documentation you need to use webhooks and api's to integrate ticketing and faq's into your own or 3rd party applications.

In the security section, we've also covered subjects such as datacenter- and network-security, application and product security, and an overview of our dataprocessors/subcontractors.

While we're working on the 2.0 version of the Socialboards API, please refer to v1.0 found on https://socialboardsinbox.docs.apiary.io/#

Getting access to the platform

If you don't have a user for our platform yet you can contact us at https://socialboards.com/no/kontakt-oss/ to get an invite.

If you have an account you can also invite more members to the platform yourself via your Socialboards settings page. Note that these actions require you to have administrator privileges.

All set? Let's start integrating!

If you're all set you can move on to getting started with the Ticket API.