Skip to main content
Nabil SemaanSocial Intelligence OS

Integrations

Platform integrations, described honestly

Social Intelligence OS is designed to work with the platforms below through their own official authorisation and API mechanisms.

What follows describes integration architecture and the conditions each integration depends on. It is not a statement that any provider connection is currently live.

Integration availability varies by provider, API access, permissions, account type and platform approval.

Supported platforms

Seven providers, seven different sets of conditions

Each entry sets out what the integration architecture targets and the provider-specific constraints that determine whether it can operate. No provider is marked as connected, approved or live.

X

Integration architecture for publishing posts from a connected X account and retrieving the post-level metrics the API exposes for it.

  • Provider API integration architecture available
  • Activation may require credentials
  • Platform review may be required
  • Feature availability depends on granted scopes

What the architecture targets

  • Account connection through the provider's official authorisation flow
  • Governed publishing of authorised posts
  • Retrieval of post metrics where the API makes them available
  • Public-comment workflows where supported by the access level held

Provider constraint. Available endpoints, rate limits and metric fields depend on the API access tier and on the app's approval status. Some capabilities are unavailable at lower access levels regardless of the scopes a user grants.

YouTube

Integration architecture for video publishing to a connected channel and retrieval of the analytics the platform exposes for that channel's content.

  • Provider API integration architecture available
  • Activation may require credentials
  • Platform review may be required
  • Feature availability depends on granted scopes
  • Capability varies by provider

What the architecture targets

  • Channel connection through the provider's official authorisation flow
  • Governed upload and publication of authorised video
  • Retrieval of video and channel analytics where available
  • Public-comment workflows where supported

Provider constraint. Upload and analytics scopes are separately granted, and applications using sensitive scopes are subject to the provider's verification process. Quota is finite and is set by the provider.

Instagram

Integration architecture for publishing to a connected professional account and retrieving the insights the platform makes available.

  • Provider API integration architecture available
  • Activation may require credentials
  • Platform review may be required
  • Feature availability depends on granted scopes
  • Capability varies by provider

What the architecture targets

  • Account connection through the provider's official authorisation flow
  • Governed publishing of authorised content
  • Retrieval of media and account insights where available
  • Public-comment workflows where supported

Provider constraint. Publishing capability is restricted to eligible professional account types and requires the corresponding permissions. Personal accounts, and some media formats, are outside what the API supports.

Facebook

Integration architecture for publishing to a connected Page and retrieving the Page and post insights the platform exposes.

  • Provider API integration architecture available
  • Activation may require credentials
  • Platform review may be required
  • Feature availability depends on granted scopes
  • Capability varies by provider

What the architecture targets

  • Page connection through the provider's official authorisation flow
  • Governed publishing of authorised content
  • Retrieval of Page and post insights where available
  • Public-comment workflows where supported

Provider constraint. Page-level permissions are granted by a person with the appropriate role on that Page, and advanced access to several permissions requires the provider's app review.

LinkedIn

Integration architecture for publishing to a connected organisation page and retrieving the share statistics the platform exposes.

  • Provider API integration architecture available
  • Activation may require credentials
  • Platform review may be required
  • Feature availability depends on granted scopes
  • Capability varies by provider

What the architecture targets

  • Organisation or member connection through the provider's official authorisation flow
  • Governed publishing of authorised content
  • Retrieval of share and follower statistics where available

Provider constraint. Access to organisation publishing and analytics products is granted by the provider on a per-application basis, and the available fields differ between member and organisation contexts.

Threads

Integration architecture for publishing to a connected Threads account and retrieving the insights the API exposes for it.

  • Provider API integration architecture available
  • Activation may require credentials
  • Platform review may be required
  • Feature availability depends on granted scopes
  • Capability varies by provider

What the architecture targets

  • Account connection through the provider's official authorisation flow
  • Governed publishing of authorised posts
  • Retrieval of post insights where available
  • Public-reply workflows where supported

Provider constraint. The API surface is comparatively young and continues to change. Capabilities available at one point may be added to, altered or restricted by the provider.

TikTok

Integration architecture for publishing video to a connected account and retrieving the video metrics the platform exposes.

  • Provider API integration architecture available
  • Activation may require credentials
  • Platform review may be required
  • Feature availability depends on granted scopes
  • Capability varies by provider

What the architecture targets

  • Account connection through the provider's official authorisation flow
  • Governed publication of authorised video
  • Retrieval of video metrics where available

Provider constraint. Content posting capability is subject to the provider's audit process, and unaudited applications are limited in how published content may be distributed. Available metrics depend on the products granted to the application.

Account connection

Connected social accounts

Users may connect supported social accounts through each provider's official authorisation process. Social Intelligence OS uses permissions granted by the user only to provide requested publishing, analytics and related account-management functionality. Available capabilities depend on the provider, the account type, permissions and API access.

Connecting an account

A connection is made through the provider's own authorisation screen. Social Intelligence OS never asks for a social-platform password, and never uses one.

Disconnecting an account

Users may disconnect a connected social account to prevent future access through that connection. Access can also be revoked from the provider's own connected-applications controls.

What disconnection does and does not do

Disconnecting stops future access. It does not delete content already published to the platform, and some historical records may be retained where necessary for security, audit, dispute resolution, legal obligations or as evidence of a past authorisation.

Read the full data deletion process

How access is obtained

Social Intelligence OS uses official provider authorisation and API mechanisms. It does not rely on credential sharing or unauthorised scraping for connected-account functionality.

No credential sharing

Social-platform passwords are never requested, handled or stored. Every connection runs through the provider's own authorisation flow.

Scope-bound access

A connection can only do what the user authorised. Where a scope was not granted, the corresponding capability does not operate.

Simulation stays labelled

Where a provider is not activated, a demonstration environment may be used. Anything it produces is labelled as simulated, including in exports and client reports.

Next step

Assessing an integration request?

The product page sets out capabilities and their stated limits; the security page describes how external actions are governed. If something is still unclear, ask.
Product capabilitiesContact