DEV Community

Cover image for APIDOG March Updates: Unlimited Sprint Branches, AI Sidebar & Enhanced Test CLI
Preecha
Preecha

Posted on

APIDOG March Updates: Unlimited Sprint Branches, AI Sidebar & Enhanced Test CLI

February shipped eight releases focused on MCP debugging and Test Suite orchestration. March focuses on accessibility and collaboration: free users now get unlimited sprint branches and API versions, published docs support multi-turn AI conversations, and CLI execution now works with sprint branch test scenarios.

Try Apidog today

Here’s what changed and how to use it.

⭐ New Updates

🔥 Unlimited Sprint Branches and API Versions Are Now Free

Apidog’s free version now supports unlimited sprint branches and API versions.

Previously, these capabilities were limited to paid plans. Now any team can use them to:

  • Develop features in isolated branches
  • Test experimental API changes without affecting the main branch
  • Maintain multiple API versions at the same time
  • Publish versioned API documentation
  • Model API work in a git-like workflow directly inside Apidog

A practical workflow looks like this:

  1. Create a sprint branch for a feature or breaking API change.
  2. Modify endpoints, schemas, examples, and tests in that branch.
  3. Run debugging and test scenarios against the branch.
  4. Review the API contract before merging changes back to the main branch.
  5. Publish or maintain the relevant API version for consumers.

Sprint branches are useful when multiple developers are working on API changes in parallel. API versions are useful when you need to keep older API contracts available while developing or publishing newer ones.

Image

✅ Optimizations

📄 Ask AI in Published Docs: Sidebar and Multi-Turn Conversations

Ask AI in published documentation has been redesigned.

Instead of appearing as a search box overlay, Ask AI now lives in a persistent sidebar. This makes it easier for developers to read the docs and ask questions without losing context.

The feature now supports multi-turn conversations, so users can ask follow-up questions instead of starting over each time.

Example usage:

  1. Open the published API documentation.
  2. Ask a question such as: “How do I authenticate requests?”
  3. Follow up with: “Show me an example request.”
  4. Continue with: “What errors should I handle?”

This makes published docs more useful for onboarding, troubleshooting, and API integration support.

Image

🔒 Enhanced Project Invitation Security

Project invitation links are now scoped to the invited account.

This prevents invitation links from being reused by unintended users or shared across teams. For teams managing sensitive APIs, this helps reduce unauthorized access caused by forwarded or leaked invitation URLs.

Recommended workflow:

  1. Invite the intended team member directly.
  2. Ask the user to accept the invitation from the invited account.
  3. Periodically review project members and remove unused access.

⚡ Test Scenario CLI Execution in Sprint Branches

Test scenarios can now be executed via CLI within sprint branches.

This is useful for teams that run automated API checks before merging feature work into the main branch. Instead of only validating the main API contract, you can now validate sprint branch changes earlier in the development workflow.

A typical CI/CD flow:

# Example CI flow structure
steps:
  - checkout-code
  - install-dependencies
  - run-api-tests-for-sprint-branch
  - block-merge-if-tests-fail
Enter fullscreen mode Exit fullscreen mode

Use this capability to:

  • Validate API contract changes before merge
  • Catch regressions in feature branches
  • Run branch-specific test scenarios in automation
  • Keep sprint branch workflows aligned with main-branch quality checks

👥 Team Member List Export

Teams can now export their member list directly from Apidog.

This is useful for:

  • Access audits
  • Compliance reporting
  • Onboarding and offboarding reviews
  • Maintaining offline records of project access

A simple access review process:

  1. Export the team member list.
  2. Compare it against your internal team roster.
  3. Identify users who no longer need access.
  4. Update project permissions as needed.

🔧 Adjustments

📛 “Cases” Renamed to “Test Cases”

The display name “Cases” has been updated to “Test Cases” throughout the interface.

This improves clarity and makes the feature easier to identify when creating, organizing, or reviewing tests.

🔐 Certificate Information in Post Processor Scripts

Post processor scripts now support pm.response.socketSession.

This allows test scripts to access certificate information for the endpoint. Security-conscious teams can use this to validate TLS-related details as part of automated test assertions.

Example use cases:

  • Inspect endpoint certificate information during testing
  • Add TLS-related checks to automated API validation
  • Include certificate details in debugging or reporting workflows

🐞 Bug Fixes

Apidog resolved 10 bugs this month:

  • Fixed an issue where proxy configuration was not effective when automated tests referenced endpoints across projects.
  • Fixed an issue where the connection was not released after debugging Socket.IO in some cases.
  • Fixed an issue where configuring a custom navigation bar in documentation mistakenly displayed internal folders, resulting in 404 errors.
  • Fixed an issue where test reports generated from legacy versions could not be viewed in the v2.8.20 desktop client.
  • Fixed the issue where the Word format option was missing when exporting data.
  • Fixed an issue where Body parameters in XML and Plain formats were not correctly imported when importing HAR files.
  • Fixed an issue where data containing Parameters in Swagger 2.0 could not be imported in certain cases.
  • Fixed an issue where invalid parent pre and post processor references were not cleaned up when exporting data in Apidog format.
  • Fixed an issue where, in request-first mode, response validation of endpoint request history could not be viewed.
  • Fixed an issue where the certificate status of custom domains could not be updated in real time.

🌟 Looking Ahead

March’s updates make Apidog more accessible for teams building, testing, and documenting APIs in parallel.

The key implementation takeaways:

  • Use unlimited sprint branches to isolate API work.
  • Use API versions to maintain multiple published contracts.
  • Use Ask AI in docs to improve developer self-service.
  • Run test scenarios from the CLI in sprint branch workflows.
  • Export team members regularly for access reviews.
  • Use pm.response.socketSession when certificate-level validation matters.

💬 Join the Conversation

Connect with fellow API engineers and the Apidog team:

  • Join our Discord community for real-time discussions and support.
  • Participate in our Slack community for technical conversations.
  • Follow us on X (Twitter) for the latest updates.

P.S. For the full details on all updates, check the Apidog Changelog.

Best Regards,

The Apidog Team

Top comments (0)