Workflow 1
Registration validation
Connect this capability to the academy context instead of managing it as a separate operational island.
R
Available
Email verification integration
Verify email addresses with your Reoon account
Connect Reoon to check addresses before high-value communications and improve the quality of learner and lead data entering your workflows.
Reduce avoidable delivery failures
Improve lead and registration quality
Use verification before important sends
Connected workflow
Bring your Reoon API key
R
Reoon
Your provider account
AL
AcademyLauncher
Connected academy workflow
Credential
Customer-supplied API key
Billing
Verification usage is billed by Reoon
Control
Choose when verification runs
What you can connect
Make Reoon part of the learner journey
Use the provider where it creates value while AcademyLauncher keeps the workflow connected to users, products, learning and operations.
Workflow 2
Lead-import quality checks
Connect this capability to the academy context instead of managing it as a separate operational island.
Workflow 3
Pre-campaign list hygiene
Connect this capability to the academy context instead of managing it as a separate operational island.
Connection process
From provider account to academy workflow
The exact authorization fields vary by provider, but the ownership model remains clear throughout setup.
01
Choose the connection
Select Reoon from the AcademyLauncher integration settings for the academy you are configuring.
02
Authorize securely
Complete the bring your reoon api key process and provide only the access required for supported workflows.
03
Test the workflow
Confirm the connection before enabling Reoon for instructors, learners or live academy operations.
04
Stay in control
Monitor the provider account and rotate, revoke or replace the connection whenever your academy requires it.
Ownership and trust
A connection should remain understandable and reversible
Provider integrations are most useful when your team knows which account is connected, what it enables and how to remove or replace it.
- Customer-supplied API key identifies the connection
- Verification usage is billed by Reoon
- Choose when verification runs
- Access should be limited to supported academy workflows
The AcademyLauncher standard
Your connection—not a black box
AcademyLauncher connects the provider to a useful academy experience while preserving a visible path back to the account, credential and permissions behind it.
Read our product principlesRelated connections
Build the rest of the workflow
Connect Reoon
Put Reoon to work inside your academy.
Bring the provider relationship you control and connect it to a coherent AcademyLauncher workflow.
Reduce avoidable delivery failures
Improve lead and registration quality
Use verification before important sends