Team & Project Management

Teams

Teams are the top-level organizational unit in Euriqa. Each team has its own isolated projects, members, and settings. Create teams for your organization, department, or squad.

Creating a Team

curl -X POST https://app.euriqa.dev/api/teams \
  -H "Content-Type: application/json" \
  -H "Cookie: <session-cookie>" \
  -d '{
    "name": "Frontend Squad"
  }'

The user who creates a team is automatically assigned the Owner role.

Listing Teams

Retrieve all teams you belong to:

curl https://app.euriqa.dev/api/teams \
  -H "Cookie: <session-cookie>"

Team Members

Each team member is assigned a role that determines their permissions. The team roster shows avatar, name, email, and role for every member.

Roles

Adding Members

Add a user directly to a team (requires Owner or Admin role):

curl -X POST https://app.euriqa.dev/api/team-members \
  -H "Content-Type: application/json" \
  -H "Cookie: <session-cookie>" \
  -d '{
    "teamId": "your-team-id",
    "userId": "user-id",
    "role": "member"
  }'

Listing Members

curl https://app.euriqa.dev/api/team-members?teamId=your-team-id \
  -H "Cookie: <session-cookie>"

Returns a list of all members with their user details, role, and join date.

Invitations

Invite collaborators to join your team via email. Invitations are team-scoped — recipients join a specific team, not the entire platform.

Sending an Invitation

curl -X POST https://app.euriqa.dev/api/invitations \
  -H "Content-Type: application/json" \
  -H "Cookie: <session-cookie>" \
  -d '{
    "teamId": "your-team-id",
    "email": "colleague@company.com",
    "role": "member"
  }'

The invitee receives an email with the team name and the name of the person who invited them. Invitations expire after 7 days for security.

Accepting or Declining

Invitees can accept or decline invitations from the invitations page in the dashboard, or via the API:

# Accept an invitation
curl -X PATCH https://app.euriqa.dev/api/invitations/invitation-id \
  -H "Content-Type: application/json" \
  -H "Cookie: <session-cookie>" \
  -d '{
    "status": "accepted"
  }'

# Decline an invitation
curl -X PATCH https://app.euriqa.dev/api/invitations/invitation-id \
  -H "Content-Type: application/json" \
  -H "Cookie: <session-cookie>" \
  -d '{
    "status": "declined"
  }'

Listing Invitations

View all invitations for a team and their statuses:

curl https://app.euriqa.dev/api/invitations?teamId=your-team-id \
  -H "Cookie: <session-cookie>"

Invitation statuses include: pending, accepted, declined, and expired.

Projects

Projects live within teams and provide isolated environments for your test data. Create one project per repository, per service, or per test suite — whatever makes sense for your workflow.

Creating a Project

curl -X POST https://app.euriqa.dev/api/projects \
  -H "Content-Type: application/json" \
  -H "Cookie: <session-cookie>" \
  -d '{
    "name": "Web App E2E Tests",
    "teamId": "your-team-id"
  }'

Listing Projects

curl https://app.euriqa.dev/api/projects?teamId=your-team-id \
  -H "Cookie: <session-cookie>"

Updating a Project

curl -X PATCH https://app.euriqa.dev/api/projects/your-project-id \
  -H "Content-Type: application/json" \
  -H "Cookie: <session-cookie>" \
  -d '{
    "name": "Web App E2E Tests (Production)"
  }'

Deleting a Project

Deleting a project permanently removes all associated test data, runs, API keys, and webhooks. This action requires the Owner or Admin role.

curl -X DELETE https://app.euriqa.dev/api/projects/your-project-id \
  -H "Cookie: <session-cookie>"

Project Settings

Each project has its own configuration that controls data retention, flakiness behavior, and integrations. Update settings via the dashboard or the API.

Example: Update Project Settings

curl -X PATCH https://app.euriqa.dev/api/projects/your-project-id \
  -H "Content-Type: application/json" \
  -H "Cookie: <session-cookie>" \
  -d '{
    "dataRetentionDays": 60,
    "flakinessThreshold": 0.5,
    "autoQuarantine": true
  }'

Additional per-project resources managed separately:

• API Keys — Generate, name, activate/deactivate, and track usage.
• Webhooks — Configure event notifications to external services.

Onboarding

New users are guided through a 3-step onboarding wizard that ensures they are productive within minutes of signing up.

Step 1: Team

Create a new team or accept a pending invitation to join an existing team.

Step 2: Project

Create your first project within the team. Give it a descriptive name that matches your repository or service.

Step 3: Configuration

Set up the Playwright reporter with your project credentials. The wizard provides your API key and project ID, along with a ready-to-copy configuration snippet.

Onboarding API Endpoints

The onboarding wizard uses the same APIs available for programmatic access: