In Apidog, projects are the core workspace where you design, test, and document your APIs. This guide covers creating, managing, and organizing projects within your team.
Choose the Project mode before creation
Project mode cannot be switched after the Project is created. Review Create a New API Project before creating the Project. For an enterprise pilot migration, use Migrate and Validate Your API Data to select the mode, source, and representative asset before expanding the migration.
To create a new project, navigate to your team and click New Project. During project creation, you can configure the project details and specify how existing team members can access the project.
Use Other Members' Project Permissions to set the project roles of existing members in the team:
Team Members are assigned the selected project role. If no role preference has been saved for the current team, Read-only is selected by default.
Team Owners and Team Admins are always assigned the Admin project role, regardless of the selected option.
Guests are always assigned the Forbidden project role and cannot access the project.
To assign roles individually, select Customize and configure a project role for each member.
Apidog remembers your most recent selection for each team and uses it as the default the next time you create a project in that team.After creating the project, you can change its name and icon under Settings → Basic Settings.
This section displays all the endpoints of the current project and provides statistics on testing coverage. It shows the percentage of endpoints that have associated test steps, as well as the percentage that have been tested within test scenarios. These statistics are valuable for evaluating the thoroughness of the API testing and their overall reliability.
Core Data:
Coverage of endpoint case: The number of endpoints with associated cases / Total number of endpoints. This is mainly used to check if individual endpoints have corresponding cases.
Average cases per endpoint: The total number of cases / Total number of endpoints. This is mainly used to assess the overall completeness of endpoint cases.
Endpoints without cases: This shows the number of endpoints that have no cases.
Coverage of test scenario: The number of endpoints covered in test scenarios / Total number of endpoints. This is mainly used to assess the extent to which endpoints are covered by automated tests.
Endpoints not covered by any test scenario: This shows the number of endpoints that are not yet covered by automated tests.
INFO
Data calculation is asynchronous, so there may be a delay. If discrepancies occur, refresh after a moment to confirm.
