Skip to main content

TOS Pages

Overview​

Some social networks requires you to provide Terms of Service URL and Privacy Policy URL and to fit with their conditions to offer access for their API. With Mixpost you can generate these pages in seconds.

Generate TOS pages​

  1. In Mixpost Dashboard, navigate to the Admin Console then click on Pages.
  2. Click on Generate samples.
  3. Upload logo, input brand name, email and register url.
  4. Click on Generate.
note

Many social networks, such as TikTok, require a fully developed website to approve your application. We recommend integrating or adapting our samples into your existing website to meet these requirements effectively.

Remove page prefix​

By default, TOS pages have a prefix after the domain in the url. Example:

https://example.com/pages/terms

If you choose to use pages directly from your Mixpost instance rather than from your main website, you must remove the pages prefix. This adjustment will allow your Mixpost instance to function seamlessly like a website.

To remove the pages prefix, set the MIXPOST_PUBLIC_PAGES_PREFIX environment variable to an empty string by adding the following line to your environment configuration:

MIXPOST_PUBLIC_PAGES_PREFIX=''

Now, your homepage will display the content defined under Admin Console -> Pages as the homepage information.

You will be able to access the Mixpost Dashboard like this:

https://example.com/<MIXPOST_CORE_PATH>
Replace <MIXPOST_CORE_PATH> with your own value

<MIXPOST_CORE_PATH> is a placeholder for the MIXPOST_CORE_PATH environment variable — the path prefix Mixpost is served under.

  • Set to a prefix, for example mixpost — use that value: https://example.com/mixpost/...
  • Empty — Mixpost is served from the root of your domain, so remove the placeholder and the slash that follows it: https://example.com/...

MIXPOST_CORE_PATH is empty by default in Pro v7+ and Enterprise v8+. In earlier versions, and in Lite, it defaults to mixpost.

Callback URLs — callback/..., inbox-webhook/..., uninstall-callback/... and, in Enterprise, payment-webhook — can carry a different prefix from the rest of your instance, because they follow MIXPOST_CALLBACK_PATH whenever that variable is set. For the OAuth Redirect URI you do not have to assemble it at all: the provider's service form in the Mixpost dashboard shows the exact URL, ready to copy.

On this page