Get Project

​

Path Parameters

​

Response

# Using project ID
curl -X GET 'https://api.frontier.example.com/v1beta1/projects/3f4a5b6c-7d8e-9f0a-1b2c-3d4e5f6a7b8c' \
  -H 'Authorization: Bearer <token>'

# Using project name
curl -X GET 'https://api.frontier.example.com/v1beta1/projects/data-platform' \
  -H 'Authorization: Bearer <token>'

​

Response Example

{
  "project": {
    "id": "3f4a5b6c-7d8e-9f0a-1b2c-3d4e5f6a7b8c",
    "name": "data-platform",
    "title": "Data Platform",
    "org_id": "9f256f86-d3c4-4a6e-b89a-1e9a23c5d78e",
    "metadata": {
      "team": "engineering",
      "department": "data",
      "cost_center": "cc-1234"
    },
    "created_at": "2024-01-20T09:15:00Z",
    "updated_at": "2024-02-15T14:30:00Z",
    "members_count": 12
  }
}

​

Error Responses

​

Common Errors

• 400 Bad Request: Invalid project ID format
• 401 Unauthorized: Invalid or missing authentication token
• 404 Not Found: Project not found or you don’t have access to it
• 500 Internal Server Error: Server encountered an unexpected error

​

Notes

• You can use either the project UUID or name/slug to retrieve a project
• The service automatically detects whether the provided identifier is a UUID or name
• Access control is enforced - you must have at least read permission on the project
• Disabled projects can still be retrieved if you have the appropriate permissions