A public app is one any SplashSend account can install, such as your booking system or your reviews tool connecting to SplashSend. Each account connects it through SplashSend's allow screen and agrees to what it asks for. Once we've checked it, it's listed in Apps for every account, with your name on it, free to install.

This article is for developers. For an app only your own account uses, see Making your own app with AI.

Make it

Click Apps in the menu, then Apps you've made. Choose Every SplashSend account and click Continue.

Make an app, with Every SplashSend account chosen.
Choose Every SplashSend account.

Fill in its name, who makes it, what it does and where it's listed in Apps. Then tick what it needs. People see that list, in full sentences, before they allow it, so ask only for what it uses.

The Make an app window, with the app's name, who makes it, what it does, where it's listed and what it needs.
What people see about your app.

Add the page on your site that starts connecting to SplashSend, under Where an install starts, and the address people come back to, under Where people go after they agree. Add its website, privacy policy and terms too, then click Make it.

The rest of the window: where an install starts, where people go after they agree, and its website, privacy policy and terms.
Where an install starts, and where people come back to.

Copy its client secret straight away. You won't see it again. Keep it on your server, never in a web page or a phone app.

Lumen Reviews is made, with its client ID and client secret to copy.
The client secret is shown once.

Build it with your AI

The app's page has a brief for the AI tool you build with. It covers connecting an account with OAuth, keeping tokens fresh, what the app may do and what to do when an account removes it. The client secret isn't in it.

The app's page, with Build it with AI and its brief.
A public app's brief.

The steps are also on the developers page, under Connecting a public app, and in the guide for AI tools at splashsend.com/developers/llms.txt.

Try it

Under Try it, install it on your own account to see the allow screen people will see. There it installs in test mode, so nothing it does starts a drip or sends an email. Switch it to live when you're ready.

To let someone else try it before we've checked it, send them the Install link for testers. Their allow screen has a note saying SplashSend hasn't checked it yet.

Try it, with the app installed on the maker's account in test mode and the install link for testers.
Try it on your own account, or send the install link.

Sending it to us

Under Before you send it, we check, the page tests a few things for you. It checks that its privacy policy opens, that its install address leads to the allow screen, that its return addresses use https and that it has worked on your account. It also names any permission the app hasn't used yet.

Before you send it, we check, with four checks passed and one permission it hasn't used, and Send it to us.
The checks before you send it.

When it's ready, click Send it to us. A person at SplashSend tries it and checks that it asks only for what it uses. Its line on Apps you've made shows where it's got to.

  • Being checked: we have it.
  • Changes asked for: its page says what to change. Change it and send it again.
  • In Apps: it's listed for every account.
  • Stopped: we've stopped it, and it no longer works on any account.

If a listed app's name or return addresses change, or it asks for more, it goes back to be checked. Accounts that installed it carry on, and new accounts can install it again once it's checked.

Good to know

  • An account can make up to 10 public apps.
  • Each account that installs it can make 100 requests a minute through it.
  • No public app can subscribe someone who unsubscribed, whatever it asks for. It sends an email only if it asks to send campaigns and the account allows it.
  • Make a new secret on its page replaces the client secret. The old one stops working at once.