Release v3.4.1
Pearsana services now use branded, professional domain names across all environments.
What's new
Custom Pearsana domains
Partners and users now access Pearsana through clean, branded URLs instead of generic cloud-generated addresses. This makes integration easier for partners and provides a more professional experience for everyone.
| Environment | API | Authentication |
|---|---|---|
| Production | api.pearsana.com | auth.pearsana.com |
| Demo (UAT) | sandbox.api.pearsana.com | sandbox.auth.pearsana.com |
Highlights:
- Branded API endpoints — partners integrating with the Pearsana API now connect via
api.pearsana.com - Branded authentication — login and account flows use
auth.pearsana.com - Environment-specific — each environment (production, demo, test, development) has its own dedicated domains
- Automatic provisioning — custom domains are set up automatically as part of the deployment process, with no manual configuration needed
- Secure by default — all custom domains use verified SSL certificates for encrypted connections
Need help?
Email support@pearsana.com — the team can help with API integration, domain configuration, or anything else.