Get Started Now!An important security enhancement to our API token system makes it easier to identify and manage your tokens while preparing for even more security improvements ahead.
What’s Changed
All newly created API tokens now use a friendlier, more secure syntax with clear prefixes:
Before
xxxx-xxxx-xxxx-xxxx-xxxx
After
mfb_xxxxxxxxxxxxxxxxxxxxxxxx # Branch tokens
mfo_xxxxxxxxxxxxxxxxxxxxxxxx # Organization tokens
Enhanced Token Security
Better Token Management
The new prefixed format makes it immediately clear what type of token you’re working with:
mfb_prefix for Branch tokens - scoped to specific repositories and branchesmfo_prefix for Organization tokens - broader access across your entire organization
Enhanced Security
This change is part of our ongoing commitment to security best practices:
- Clear identification prevents accidental misuse of tokens
- Scope visibility helps teams understand token permissions at a glance
- Future-proofing for additional security enhancements coming soon
What You Need to Do
Existing tokens continue to work normally - there’s no immediate action required. However, we recommend:
- Regenerate tokens when convenient to take advantage of the new format
- Update documentation to reflect the new token format
- Review token usage to ensure you’re using the most appropriate token type
Questions?
If you have any questions about the new token format or need help with token management, don’t hesitate to reach out to us at hello@mergefreeze.com or check our API documentation.
The security of your deployments is our top priority, and we’re committed to continuously improving our platform to keep your code safe.