Endpoint
Authentication
Requires a Personal API Access Token.Header
Request
Headers
| Header | Value | Required |
|---|---|---|
| Authorization | Bearer | Yes |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
Query Parameters
None.Response
Success Response (200 OK)
Response Fields
| Field | Type | Description |
|---|---|---|
| success | boolean | Indicates if the request was successful |
| resultList | array[object] | List of environments accessible from the project |
| resultCount | integer | Total number of environments |
Environment Object
| Field | Type | Description |
|---|---|---|
| environmentName | string | Environment name |
| description | string | Environment description (optional) |
Error Response (400 Bad Request)
Error Response (401 Unauthorized)
Error Response (403 Forbidden)
cURL Example
Permissions
- User must have any permission in the project (read access)
Notes and Warnings
- Project Membership: User must be a member of the project to access environments
- Returns only environments accessible through project membership
- Project Access: If user doesn’t have access to the project, returns 403 Forbidden
Related Documentation
- List Environments - Get all environments (admin only)
- Projects API - Project management endpoints
- Authentication Guide - How to obtain and use API tokens

