Skip to content
Sign inStart my free trial
Developer platform

Build an app your mailfloss users can connect

Let people connect their mailfloss account to your app, approve the access it needs, and disconnect it from their account settings.

What is the mailfloss developer platform?

The mailfloss developer platform lets you register an app that other mailfloss users authorize to work with their accounts. It uses OAuth to connect your app to the REST API without asking users to share their passwords or API keys. Start with the app-building guide, test your connection, and prepare your app for review.

Choose the path for what you’re building

Working with your own account? Start with the API Quick Start. An account owner or admin can create an API key for a tool that works with that account. For verification capabilities and API examples, visit the email verification API page.

Building an app for other mailfloss users? Register your app and let each user approve a connection through mailfloss. Your app receives access for that user’s account, within the permissions they can grant. You can build the connection around your product’s workflow without collecting each user’s API key.

From your first connection to app review

01
Register your app
An owner or admin opens Developers → Your apps in the mailfloss dashboard. Add your app’s name, redirect URLs and the permissions it needs. The app-building guide covers the connection flow and how to handle tokens on your server.
02
Make the connection work for your users
Send users to mailfloss to sign in and approve your app’s requested access. The access they grant is limited by your app’s permissions and their role in the account. They can disconnect your app under Account Settings → Connected apps. Follow the guide through connection, refresh and disconnect. Test with your own account before you prepare the screenshots and demonstration for review.
03
Show what your app does
Open your app’s Get verified tab when you’re ready to submit. Prepare a clear description, working website and support links, a privacy policy, screenshots, a demonstration video, and setup instructions. Explain why your app needs its permissions. Use made-up data in review materials, and follow the app review guidelines for the complete requirements.

Know what verification changes

An unverified app can have up to 100 active OAuth connections. More than one connection from the same account can count toward that limit. Users see a notice that mailfloss hasn’t verified the app when they connect it.

Approval replaces that notice with a Verified by mailfloss badge and removes the unverified-app connection limit. Other controls, including rate and plan limits, still apply.

Verification reflects a review of the submitted information at that time. It is not a security audit, an endorsement, or a guarantee of the app’s identity, performance, security or legal compliance. Approval is not automatic, and review-time targets are not guaranteed deadlines.

Questions before you start

No. An app built with mailfloss’s OAuth connection flow receives an access token after the user approves it. Keep the connection implementation aligned with the app-building guide.

Start with your app’s connection flow

Follow the guide from registering your app through connecting and disconnecting a mailfloss account.