Collections
Collections are the primary way to organize your API requests in Nidra. Think of them as folders that group related requests together.
What is a Collection?
A collection is a container for organizing related API requests. Collections help you:
- Group requests for a specific API or project
- Share related requests with your team
- Import and export groups of requests
- Organize your workspace logically
Creating Collections
To create a new collection:
- Click the "New Collection" button in the sidebar
- Give your collection a name
- Optionally add a description
- Click "Create"
Managing Collections
Renaming Collections
Deleting Collections
Organizing Collections
You can organize collections by:
- API/Service (e.g., "GitHub API", "Stripe API")
- Project (e.g., "Mobile App Backend", "Admin Dashboard")
- Environment (e.g., "Production Tests", "Development")
- Feature (e.g., "Authentication", "User Management")
Collection Settings
Each collection can have its own settings:
- Default authentication
- Base URL
- Default headers
- Variables scoped to the collection
Importing Collections
Nidra supports importing collections from multiple sources:
- Swagger/OpenAPI: Import complete API definitions
- Postman: Migrate existing Postman collections
- Nidra Format: Import from other Nidra instances
Learn about importing Swagger → Learn about importing Postman →
Exporting Collections
Export your collections to:
- Share with team members
- Back up your work
- Use in other tools
Best Practices
- Use descriptive names: Make collection names clear and specific
- Group logically: Organize requests in a way that makes sense for your workflow
- Document your collections: Add descriptions to help team members understand the purpose
- Keep collections focused: Don't mix unrelated APIs in the same collection
Next Steps
- Learn about Requests within collections
- Explore Environments for managing variables
- Build Conduits to create test flows