Say Goodbye to Plaintext Secrets: Freshworks FDK v9.5.0 Masks Secrets Safely!

Hey developers, time to grab a coffee (or maybe something stronger).
We need to talk — about your app’s secrets.

If you’ve been happily pasting API keys, tokens, or secret sauce formulas into your Freshworks app’s installation page, guess what?

That party is officially over!

👉 Starting with Freshworks FDK v9.5.0, secure iparams are getting the ultimate makeover:
They’ll be masked — forever.

No more peeking.
No more copy-pasting from the UI.
And definitely no more “I forgot to delete that secret” horror stories.

⏰ Deadline: 31st December 2025

Miss it, and your app won’t make the cut for new submissions or upgrades. Oof.

🎭 What’s This Masking Magic All About?

🔐 Before Freshworks FDK v9.5.0:

Secure iparams (you know — API keys, passwords, private tokens) sat there on the config page, looking all plain and exposed.
Anyone with config access could:

See them
Copy them
Accidentally screenshot them

🔐 After Freshworks FDK v9.5.0:

Once saved, secure iparams will be masked — yep, hidden behind those classic password dots.
No more visible API keys or tokens just hanging out in plain sight.

Only non-sensitive fields like usernames will remain visible on the configuration page.
Secure iparams (passwords, secrets, etc.) will stay locked down — safe from:

Screenshots
UI snooping
Accidental leaks during screen shares

👉 Bottom line? Sensitive data stays secure — both on the UI and in any network calls after installation.

💥 Why Should You Care (and Care Now)?

Let’s be real. Most of us aren’t out here trying to leak secrets.
But accidents happen:

You share your screen during a meeting and boom — there’s your API key on display.
You forget to blur a screenshot in documentation.
You leave your desk, and your app config is open.

Masking secure iparams helps prevent these oops-moments.
Plus, it keeps your app in line with modern security standards.

And remember:

👉 If your app relies on showing secure iparams in plain text… it’s going to break.
👉 If you miss the Freshworks FDK v9.5.0 upgrade deadline… no more submissions, no more upgrades.

🛠️ What Do You Need To Do?

Good news: You don’t need to panic (yet).
But you do need to act.

1️⃣ Upgrade Your FDK Version

Update to Freshworks FDK v9.5.0 or later.

Apps built on older versions won’t be allowed after December 2025.

2️⃣ Refactor Your Code

Access your secure iparams through the Request Method using the iparam template.
Forget about plain text on the config page.

3️⃣ Test Like Your Job Depends On It

Validate that your app still works with masked iparams.
Double-check nothing’s breaking where you previously relied on visible secrets.

4️⃣ Submit Early

Don’t be that person rushing on December 31st.
Procrastination + security deadlines = 💣

🚀 Bonus Upgrades in Freshworks FDK v9.5.0

Okay, since you’re upgrading anyway, check out the other shiny features you’ll get:

✨ `currentHost` Updates

No more manually typing organization domains during installation.
Your app can now pre-fill it using currentHost.org_domain + utils.set() magic.

✨ Freshservice for MSPs Support

Build apps for Freshservice (for IT/Business Teams) and Freshservice for MSPs (for Managed Service Providers).

MSP devs, it’s your time to shine!

📘 For more technical details, head to the Freshworks Developer Docs.

❗ The Countdown Is Real

Look, December 31, 2025, might feel far away. But we all know how this goes:

First it’s June.
Then it’s August.
Blink, and it’s New Year’s Eve and you’re scrambling to update an app between parties and fireworks.

👉 Don’t do that to yourself.
👉 Don’t do that to your users.
👉 Don’t do that to your security team.

💡 FAQs We Know You’re Thinking

Q: Will masking secure iparams break my app?
A: Only if your app depends on showing them in plain text. Refactor now and you’re golden.

Q: Can I still access secure iparams after saving?
A: Absolutely — but only through the Request Method using the iparam template.

Q: What happens if I don’t upgrade before the deadline?
A: Your app won’t be accepted for new submissions or upgrades.

Q: Is there documentation?
A: Of course! Check the Freshworks Developer Docs or join the dev community.

🧠 Pro Tips to Nail This Transition

✅ Start now. Even small apps take time to refactor, test, and submit.
✅ Automate testing. Make sure masked iparams don’t cause unexpected failures.
✅ Document your changes. Future-you (or your teammates) will thank you.
✅ Share the news. From devs to PMs — everyone should know.

📌 Final Thoughts: Don’t Wait for the Mask to Slip

In 2025, apps with exposed secrets will be so last year.
Freshworks FDK v9.5.0 is giving us a gift: a safer, cleaner way to manage sensitive data.

👉 Your job? Take the gift.
✅ Upgrade your FDK
✅ Mask those secrets
✅ Ship secure apps

And remember…

🕛 31st December 2025 — the day your app either shines or sinks.

So get cracking — before that clock runs out!