Skip to main content
Shareable links are configured at the network level. The SDKs fetch the configured domain and URL patterns so your app can build links to Social+ content using your own routing scheme. The current SDKs expose this configuration differently:
The SDK reads the configured patterns. It does not create the destination screens in your app. Your app still needs routes that can open the generated URLs.

Parameters

Supported Pattern Keys

TypeScript maps content types to these pattern keys: iOS and Android return the backend patterns map directly. Check that the key you need exists before generating a link.

Generate a Post Link

Fetch the shareable-link configuration before generating a post link, then fall back gracefully if the needed pattern is missing.
Event links are the primary use case for shareable links: an app can copy or share a direct link to an event detail screen. Gate the share UI on isEnabled first, then generate the link — generateLink returns null when the event pattern is not configured.
Shareable links are available on TypeScript, iOS, and Android. Flutter has no public shareable-link configuration API in the current SDK source.

Best Practices

  • Treat missing patterns as a disabled share target for that content type.
  • Generate links only after the content exists and you have the final content ID.
  • Keep app route handling separate from link generation so deleted or restricted content can show a useful fallback screen.
  • Cache the configuration during a session if your sharing UI needs it often.

Posts Overview

Learn how posts are modeled and created.

Communities

Share community destinations after configuring community URL patterns.

User Management

Share user profile destinations after configuring user URL patterns.

Events

Share event links after configuring the event URL pattern.