Facebook

Facebook is supported in Outstand through the Bring Your Own Key (BYOK) model via Meta's Facebook Graph API. This allows you to use your own Meta app credentials to connect Facebook Pages and publish posts through Outstand's unified API.

Note: You can skip the approval process by using our Managed Keys service. Contact our support team to learn more at contact@outstand.so. Turnaround time is typically 1 business day.

Quick Information

Our application works with the following OAuth scopes:

• pages_read_user_content - Basic Facebook Page access (allows reading profile)
• business_management - Permission to manage business pages
• pages_show_list - Permission to read engagement metrics
• pages_manage_posts - Permission to publish posts
• pages_read_engagement - Permission to read engagement metrics
• pages_manage_engagement - Permission to interact with engagement

These are the scopes that are required for the integration to work.

Facebook Graph API

We utilize Meta's Facebook Graph API to connect to Facebook Pages and publish posts. The version of the API we use is v24.0.

Outstand OAuth Callback URL

When configuring your Meta app, you must add the following OAuth redirect URI:

https://www.outstand.so/app/api/socials/facebook/callback

This is where Facebook will redirect users after they authorize your app. Make sure to add this URL to:

• Facebook Login → Settings → Valid OAuth Redirect URIs
• Settings → Basic → App Domains: Add outstand.so

White-labeling authentication flow

For full white-labeling integration, you need to follow the following flow:

1. Call the /v1/social-networks/:network/auth-url endpoint to get the authentication URL. You MUST provide a redirect_uri in the request body.
2. The redirect URI must lead to a Facebook-specific callback URL in your application. We will redirect to it with a session query parameter.
3. Your callback URL must call the /v1/social-accounts/pending/:sessionToken endpoint (docs link) to get the pending connection details.
4. The response will contain a list of available pages/accounts that can be connected.
5. You can then redirect the user to a selection page where they can select the pages/accounts they want to connect.
6. Once the user has selected the pages/accounts, you can call the /v1/social-accounts/pending/:sessionToken/finalize endpoint (docs link) to finalize the connection.
7. The response will contain the connected accounts.
8. You can then use the connected accounts to post on behalf of the user.

The full flow is illustrated in the following diagram:

Media Requirements

When publishing posts with media to Facebook Pages, Outstand handles media processing automatically:

How Media Upload Works

1. Media Download: Outstand downloads the media from your provided URL server-side
2. Binary Upload: The media is then uploaded directly to Facebook as binary data
3. Post Creation: Once the media is uploaded, the post is created with the media attached

This approach ensures reliable media uploads and avoids issues where Facebook cannot access your media URLs.

Image Requirements

Video Requirements

Media URL Requirements

Your media URLs must:

• Be publicly accessible over HTTPS
• Return a valid Content-Type header (e.g., image/jpeg, video/mp4)
• Be available at the time of publishing (Outstand downloads the media when publishing)
• Not require authentication or special headers to access

Example with Media

{
  "containers": [
    {
      "content": "Check out our latest update!",
      "media": [
        {
          "url": "https://media.yoursite.com/images/update.jpg",
          "filename": "update.jpg"
        }
      ]
    }
  ],
  "accounts": ["facebook"]
}

Common Errors

Feel free to get in touch with our support team if you have any questions or need assistance with the integration.