Across four public releases—from Apidog 2.8.41 through 2.8.44—August strengthened three connected parts of enterprise API operations: governed Git connectivity, identity-driven project access, and more useful and traceable API-based administration.
Enterprise API teams increasingly manage repositories, identities, and membership through systems outside the API platform itself. This month, Apidog improves those connections while also delivering focused reliability updates across project setup, imports, branches, documentation, CLI workflows, and test execution.
The headline updates are:
- GitHub Enterprise Cloud: Connect Apidog to data-residency deployments on dedicated
*.ghe.comdomains. - SSO governance and project access: Keep enterprise SSO sessions focused on organization work and initialize project permissions through SAML Group Mapping.
- Enterprise administration APIs: Retrieve more useful organization member data, automate team onboarding with explicit project-access initialization, and bring supported API-driven administrative operations into the audit trail.
Additional environment, policy, internationalization, specification, and workflow improvements are summarized after the three headline updates.
1. ☁️ GitHub Enterprise Cloud for Data-Residency Workflows
GitHub Enterprise Cloud customers with data residency can host repositories on dedicated *.ghe.com domains instead of the public github.com domain. Until now, that created a gap for teams that wanted to use Apidog’s Git workflows without moving governed repositories outside their organization’s existing GitHub environment.
Connect to your organization’s *.ghe.com host
Organization administrators can now configure a GitHub Enterprise Cloud host together with an OAuth App Client ID and Client Secret. The authorization flow uses the configured enterprise host, allowing Apidog to access the organizations, repositories, branches, and files required by supported Git operations.
The connection applies across three practical workflows:
- Git Connection: Work with API definitions through the repository and branch controlled by your organization.
- Repository import: Import OpenAPI or Swagger files from an enterprise repository into Apidog.
- OpenAPI backup: Back up API definitions to the enterprise repository and branch selected by the team.
The result is continuity: teams can keep their repository governance and data-residency model while using Apidog’s Git-based import, backup, and collaboration workflows.
Scope: This update is limited to GitHub Enterprise Cloud data-residency deployments on dedicated *.ghe.com SaaS domains. It does not add general support for self-hosted GitHub Enterprise Server domains.2. 🛡️ Stronger SSO Governance and Project Access
Enterprise SSO should do more than authenticate a user. It should keep the session focused on the organization’s intended workspace and translate identity-provider membership into predictable access to the projects where work happens.
Keep enterprise SSO sessions focused on organization work
With SSO session isolation enabled, Apidog reduces entry points into personal teams and projects. It also limits selected actions that could move, copy, or clone organization work into personal spaces. Users stay focused on the organization and team associated with their SSO session, while administrators gain a clearer separation between enterprise and personal workflows.
These controls strengthen the intended access boundary without changing the normal experience for organizations that do not enable SSO session isolation.
Carry team membership into project-level access
SAML Group Mapping now extends beyond organization and team membership by initializing access to projects under the synchronized team. The initial project roles follow a simple rule:
| Synchronized team role | Initial access to projects under the team |
|---|---|
| Team Admin | Editor |
| Other Team Member | Read-Only |
When a mapped user is removed from the team, Apidog synchronizes the related project membership as well. This closes the operational gap between identity-provider groups, team roles, and the project permissions users need after sign-in.
Why it matters: Administrators spend less time repairing project membership after onboarding or offboarding, and users enter team projects with a clear, consistent starting level of access.
3. 📋 More Complete and Auditable Enterprise Administration APIs
Enterprise administrators often rely on APIs to inventory members, connect identity systems, and automate routine administration. Those workflows are only dependable when the API returns useful member data, onboarding behavior is explicit and protective, and automated operations remain visible to governance teams.
Retrieve more useful organization member data
The Organization Members API now provides email addresses and more reliable member names alongside existing membership information:
GET /v1/organizations/{organizationId}/members
When a member has not set a nickname, Apidog can use other available profile information for the returned name. Members without an available email address, including applicable pending or provisioned records, return an explicit null value rather than an ambiguous missing field.
This makes the API more practical for:
- Member inventory: Identify organization members with the information administrators commonly need for review.
- Automated synchronization: Use stable member data in external identity and administration workflows.
- Access review: Compare membership records without depending on a separate manual CSV export for basic details.
Assign team roles and initialize project access through the API
Enterprise administrators can now add a user to a team by email and assign a supported built-in team role through the external API:
POST /v1/team-access-grants
Each request explicitly selects both the team role—Admin, Member, or Guest—and how access to projects already under the team should be initialized. With mapped, Apidog initializes missing project access according to the selected team role while preserving existing valid project roles. With none, the user joins the team without receiving project-member permissions, so access can be assigned separately.
The endpoint also supports invitations for users who have not yet joined the organization and restoring members who previously left the team. Existing active or pending team members and Team Owners are protected from unintended changes, making repeated calls safer for automated onboarding workflows.
Scope: Project-access initialization applies to projects that already exist under the team when a user first joins or is restored. It does not continuously synchronize permissions or automatically apply to future projects, and the endpoint does not assign Team Owner, Billing Manager, or custom Team Roles.
Keep supported API-driven administration in the audit trail
Supported external administrative API operations that correspond to existing audit events are now incorporated into the audit trail. This gives governance teams better continuity between actions performed in the Apidog interface and supported actions performed through automation.
Together, richer member data, safer team-access automation, and broader audit coverage make enterprise administration easier to automate without losing the visibility required for operational review.
Scope: Audit coverage applies to supported external API operations associated with existing audit events; it should not be interpreted as universal logging of every API request or management endpoint.
✨ More Improvements
August also includes a set of focused improvements across environment configuration, enterprise policy, internationalization, specification workflows, and project administration.
Enterprise and environment management
- Organization membership policy: Enterprise administrators can restrict organization membership to members with specified email addresses, helping keep access aligned with approved identity rules.
- Invitation Reward Policy: Organizations can disable Credit rewards and related emails for invitations sent from the organization and its teams or projects.
- Faster Module Base URL navigation: When a project has more than five modules, entries after the first five collapse automatically, while search helps users locate the service configuration they need.
- Localized system emails: Apidog system emails now follow the recipient’s selected language, with English used when an Apidog language preference is unavailable.
- More manageable organization-owned teams: Organization Owners and Admins can view each Team Owner and owner status, search or filter teams by those fields, and transfer ownership for one or multiple teams. This makes organization-managed personal workspaces easier to identify and hand over when ownership changes.
- Clearer project-member management: Bulk member editing, member-detail dialogs, and permission settings are easier to work with, while Team Owner roles are protected from unsupported changes.
Project setup, imports, and specifications
- Safer mode switching during project creation: Information already entered in the project-creation form is retained when switching between General Mode and Spec Mode.
- Improved Postman file imports: Imports now support global variables and handle spaces in variable names automatically, reducing cleanup after migration.
- Better cross-file
$refsupport in Spec Mode: Endpoint previews can resolve supported request bodies, schemas, and responses stored in separate OpenAPI files. Spectral lint across referenced files, full endpoint references, and Form Mode cross-file references remain outside this scope.
Together, these improvements reduce recurring setup and administration friction without competing with the release’s three primary enterprise workflows.
🛠️ Notable Bug Fixes
August’s releases also addressed reliability issues across Git branches, OpenAPI import and export, shared documentation, CLI-created data, and test execution. The most consequential fixes fall into three workflow groups.
Safer branch, import, export, and code-generation workflows
- Apidog CLI OpenAPI imports now write to the branch selected by the user instead of incorrectly writing to the main branch.
- Release-document exports from sub-branches no longer include endpoints from unrelated modules or empty folders.
- Multi-branch merges more reliably carry endpoints, test scenarios, and other resources into the target branch.
- The Create Git Repository Connection action responds correctly during OpenAPI import.
- OpenAPI and CLI exports now respect selected modules, tags, and folders instead of unintentionally including a broader endpoint set.
- Schemas referenced across modules are preserved more reliably during code generation.
- AND-related Security Schemes are exported correctly instead of being merged into an inaccurate internal representation.
More accurate validation and shared documentation
- Strict-mode response validation now handles schemas composed with
allOfcorrectly. - Schemas referenced through
Additional propertiesappear correctly in shared API documentation. - Default examples are displayed correctly in shared documentation.
- Markdown document tabs render completely when signed-out users visit public projects.
More dependable CLI data and test execution
- Global variables created through AI or Apidog CLI no longer produce empty client-side variable names.
- Invalid tag values created by Apidog CLI no longer cause frontend access errors.
- Project-level test data created without
--scenarioremains visible in the data list. - Pre- and post-processor execution details appear in the console while an SSE request is running, rather than only after the request finishes.
- Dataset names remain visible when test runs use long-text dataset variables.
These fixes reduce the chance that a correct workflow produces the wrong branch destination, an incomplete export, missing documentation, or misleading test feedback.
🌟 What This Means
August’s headline updates strengthen three connected parts of the enterprise API operating model:
| Focus | What improves | Why it matters |
|---|---|---|
| Governed Git connectivity | Apidog can connect to GitHub Enterprise Cloud data-residency hosts on *.ghe.com for Git Connection, repository import, and OpenAPI backup. |
Teams keep repositories in the GitHub environment and branch structure their organization controls. |
| Identity-to-project access | SSO sessions reduce entry points into personal spaces, while SAML Group Mapping initializes and maintains project membership. | Onboarding and offboarding become more predictable, with less manual permission repair. |
| Auditable administration | Organization member APIs return more useful identity data, the Team Access Grant API automates protected team onboarding with explicit project-access initialization, and supported external administrative operations feed into existing audit events. | Teams can automate more administration without giving up the control and visibility needed for onboarding, inventory, access review, and governance. |
The additional environment, policy, specification, and reliability improvements make everyday workflows more dependable, but the larger direction is consistent: keeping repository governance, identity access, and administrative automation aligned as enterprise API programs grow.
💬 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) and LinkedIn for the latest updates.
P.S. For the item-by-item release notes, see the Apidog Changelog, including versions 2.8.41, 2.8.42, 2.8.43, and 2.8.44.
Best Regards,
The Apidog Team
