July’s release focuses on three areas: stronger enterprise security and access management, more dependable API migration and specification sync, and easier-to-maintain testing workflows.
API teams need confidence that credentials can be found before they become incidents, organization activity remains traceable, imported API data retains its meaning, and automated tests are easy to reuse and monitor.
This release improves those workflows across three areas:
- Enterprise security and access (Enterprise plan): Detect credential risks, audit important organization activity, and improve SCIM, SAML, and SSO workflows.
- API migration and specification sync: Preserve more Postman context and make OpenAPI/Swagger imports safer to repeat.
- Testing and workflow reliability: Reuse test assets, check when scenarios last ran, and save large environment configurations more reliably.
1. 🔐 Enterprise Security and Access
Enterprise API governance requires three connected capabilities:
- Find sensitive information before it becomes an incident.
- Trace important organization activity.
- Give the right users the right access.
July’s updates strengthen each part of that operating model.
Availability: Enterprise plan
Enterprise Secret Scanner: Find and Manage Credential Risks
API projects can contain credentials in request parameters, headers, environments, variables, scripts, examples, and authentication settings. A plain-text API key, access token, or private key can be difficult to detect across a large organization.
Use Secret Scanner to create a repeatable remediation workflow:
- Review findings at the organization level. Organization administrators can identify teams with unresolved findings and locate the relevant Team Owners or Team Admins.
- Investigate findings at the team level. Teams can review findings across projects and inspect every occurrence associated with the same secret risk.
- Navigate to the source. Each occurrence can link back to the related request, environment, variable, example, or other source resource.
- Record the resolution. Mark findings as resolved with a reason such as Revoked, False positive, or Won’t fix.
- Add internal detection rules. Team administrators can create, edit, enable, disable, or delete custom patterns for organization-specific credential formats.
This turns secret detection into an auditable process: find the source, assign ownership, remediate the issue, and document the outcome.
Enterprise Audit Logs: Trace Organization Activity
When an organization manages many members, teams, projects, and permissions, administrators need a reliable activity history. Without it, investigating an access change or sensitive operation can require manual checks across multiple systems.
Enterprise Audit Logs provide Organization Owners and Admins with a centralized event history. Each record can include:
- Operator
- Event type
- Event description
- Source IP address
- Timestamp
Filter logs by time range, event type, and operator to investigate changes involving:
- Members and teams
- Permissions
- Projects
- Login events
Use these records during security reviews, incident investigations, and internal compliance processes.
Improve SCIM, SAML, and SSO Workflows
Apidog improved SCIM 2.0 compatibility across a broader range of identity provider (IdP) integrations. User lifecycle operations and organization-level group management are more resilient to differences in SCIM fields and endpoint behavior.
For organizations using IdPs such as JumpCloud, Microsoft Entra ID, and Okta, these improvements help make provisioning and synchronization more reliable.
Enhanced SAML Group Mapping supports both:
- Single-group strings
- Multi-group arrays
This helps users receive expected organization and team roles after SSO login without disrupting existing team membership.
After SSO login, Apidog can also automatically expand and select the corresponding organization and team. This reduces workspace navigation and helps users enter the right project with the right access faster.
2. 📦 API Migration and Specification Sync
A successful migration is not just about importing data. Imported requests should remain understandable, authentication should stay usable, variables should keep their context, and repeated specification syncs should not overwrite unrelated resources.
More Complete Postman Migration
Apidog now preserves and maps more Postman data across local file imports and Postman API imports.
When migrating a collection, verify these areas:
- Collection-level authentication and endpoint-level OAuth 2.0 settings are imported more accurately.
- OAuth 2.0 Refresh Token URLs are mapped correctly.
- Variable descriptions and secret classifications can be retained.
-
form-datafile fields preserve the original filename when the local file itself cannot be transferred. - Postman API imports can include Globals, with an option to exclude them.
- Unsupported variable-name characters, such as spaces or vertical bars, are replaced with underscores.
- Repeated Postman API imports are less likely to use stale browser-cached Collection data.
| Before | Now |
|---|---|
| Authentication details could require rebuilding after migration. | More authentication and request-body settings are preserved. |
| Variable context or secret metadata could be lost. | Variables retain more useful context. |
| Globals were not included through the Postman API path. | Globals can be reviewed and imported. |
| Unsupported variable-name characters could break references. | Variable names are normalized for Apidog templates. |
| Repeated imports could occasionally use older cached data. | Repeated migration and synchronization are more dependable. |
The practical result is less post-migration cleanup and a shorter path from imported data to requests that teams can validate and run.
Safer OpenAPI and Swagger Import Workflows
OpenAPI and Swagger imports are often recurring synchronization workflows, not one-time migrations. Import errors, incomplete parsing, and incorrect resource deletion can therefore affect a project repeatedly.
Apidog now provides clearer error details when an OpenAPI or Swagger file cannot be imported. If the issue may be related to the selected specification format, the import flow provides more direct guidance for switching formats and continuing the investigation.
This release also improves several synchronization scenarios:
- Scheduled imports can process definitions returned with non-2xx HTTP responses more correctly.
- OpenAPI 3.1 imports into iteration branches preserve endpoints, Webhooks, folders, descriptions, and deprecated states more reliably.
- Folders without HTTP endpoints are less likely to be removed incorrectly when deleting resources no longer present in the source definition.
- Schema circular references are handled more reliably during import.
- Model synchronization across modules and scheduled import sources is less likely to overwrite unrelated models with the same name.
For multi-module projects, branches, and scheduled import workflows, these changes make specification synchronization safer and easier to troubleshoot.
3. 🧪 Testing and Workflow Reliability
Automation is harder to maintain when teams duplicate test assets, cannot tell when scenarios last ran, or encounter avoidable failures while saving large configurations.
Reuse Test Assets in Apidog CLI
When Apidog CLI runs scenario cases, scenario steps can now reference:
- Endpoints
- Test cases
- Other scenarios
Instead of recreating the same logic as isolated steps, compose scenarios from existing test assets.
This helps teams:
- Reuse test logic in local scripts and CI/CD pipelines.
- Keep interactive and automated testing aligned.
- Build more modular scenario workflows.
- Reduce duplicated test maintenance.
Check When Test Scenarios Last Ran
The automated test scenario list now displays the most recent run time alongside the creation time.
Use this to quickly identify:
- Scenarios that have not run recently.
- Tests that may need attention.
- Recent testing activity to share with project stakeholders.
Save Large Environment Configurations More Reliably
Large projects can accumulate invalid empty values in environment configuration. This increases request size and can occasionally cause save failures.
Apidog now removes unused empty data when saving an environment, making configuration updates more reliable for projects with many modules.
🐞 Bug Fixes and Smaller Improvements
This release also includes fixes and quality-of-life improvements:
- Fixed an issue where Runner notifications and recent run results could show an average duration of
0after a test scenario completed. - Fixed an issue where clicking Forgot password did not automatically reuse previously entered account information.
- Fixed an issue where Organization Owners could lose access to organization settings after the member limit was exceeded.
- Fixed an issue where a Team Owner could rejoin through a project invitation link with an incorrect regular-member role.
- Fixed a timezone offset in the organization member list’s recent activity time.
- Fixed an issue where cloning a project from a published documentation site could include endpoints from unpublished modules.
- Fixed an issue where test suite steps could disappear after saving in a child branch.
- Fixed an issue where Runner could fail to execute test suites in child branches.
- Fixed an issue where multi-module documentation exports could contain endpoints from modules that were not selected.
- Fixed an issue where disabling Import Authentication could incorrectly change directory authentication to No Auth.
- Improved Secret Scanner recognition for additional credential patterns.
- Fixed an issue where images in Markdown documents could fail to display in the On-Premises desktop client.
- Improved cumulative credit usage data so total increases and total consumption can be displayed more accurately.
🌟 What This Means
| Focus | What improves | Why it matters |
|---|---|---|
| Enterprise security and access | Secret Scanner, Audit Logs, JumpCloud SCIM and SAML compatibility, and faster SSO workspace navigation. | Organizations can find credential risks, trace important activity, and manage user access with fewer gaps. |
| API migration and specification sync | More Postman context is preserved, while OpenAPI and Swagger imports are safer and easier to troubleshoot. | Teams spend less time repairing imported data and face a lower risk of losing or overwriting project resources. |
| Testing and workflow reliability | CLI scenarios reuse existing assets, scenario activity is easier to see, and large environment saves are more stable. | Automated workflows become easier to compose, monitor, and maintain. |
Together, these updates provide a clearer and more reliable operational foundation for security teams, administrators, API designers, and test engineers.
💬 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.
For full details on all updates, check the Apidog Changelog.
Best Regards,
The Apidog Team
Top comments (0)