Skip to content

List Designs

Method

REST method is adopted.

HTTP Method

GET: Get design list

Naming Convention

To unify the naming of query parameters and nodes and improve readability, snake_case is used for URIs and JSON nodes in requests.

Request and Response

Headers

Meta information is set in HTTP headers, not in the response body.

Request Headers

  • Authorization
  • Content-Type
  • Accept
  • Accept-language

Response Headers

  • Content-Type

Get List

URI

GET /v1/organizations/{organization_id}/projects/{project_id}/designs

Path Parameters

Name Type Required Description
organization_id number Required Backend PostgreSQL organization ID
project_id number Required Backend PostgreSQL project ID

Query Parameters

For list retrieval, page, limit, and sort are generally defined.

Name Type Default Description
page integer 1 Page number (minimum: 1)
limit integer 20 Items per page (minimum: 1, maximum: 100)
sort string asc Sort order (asc or desc)

Response

The response is JSON.

{
  "currentPage": 1,
  "totalCount": 10,
  "list": [
    {
      "id": "42_hDDA9BNori9OTXSClduXqR_40002029:37033",
      "projectId": 42,
      "s3Key": "1/42/design/hDDA9BNori9OTXSClduXqR/40002029-37033.png",
      "frameName": "Login Screen",
      "status": 2,
      "createdAt": 1234567890000,
      "updatedAt": 1234567890000,
      "deletedAt": null,
      "createdBy": "user-id",
      "updatedBy": "user-id",
      "deletedBy": null
    }
  ]
}

Response Fields

Name Type Description
currentPage number Current page number
totalCount number Total item count
list array Array of design objects
list[].id string Design ID (format: {project_id}_{file_id}_{node_id})
list[].projectId number Backend PostgreSQL project ID
list[].s3Key string | null S3 object key
list[].frameName string | null Figma frame name
list[].status number Processing status (0-3)
list[].createdAt number Creation timestamp (epoch milliseconds)
list[].updatedAt number Update timestamp (epoch milliseconds)

Authentication

Authentication is performed using JSON Web Tokens (JWT) issued by Amazon Cognito.

Error Handling

The status codes for error handling are as follows.

Description Status Code Status Name
Missing credentials 401 Unauthorized
Insufficient permissions 403 Forbidden
Project or organization not found 404 Not Found
Internal server error 500 Internal Server Error

Processing Flow

  1. Extract organization ID and project ID from path parameters
  2. Extract pagination settings from query parameters
  3. Verify the user has access to the project
  4. Query designs from the database with pagination
  5. Return paginated response

Detailed Flowchart

flowchart TD
    Start([GET Request]) --> Auth[Auth & Parameter Extraction<br/>page, limit, sort]
    Auth --> Service[Service Layer]
    Service --> AccessCheck[Access Check]
    AccessCheck --> HasAccess{Read permission?}
    HasAccess -->|No| Err404[404 Not Found]
    HasAccess -->|Yes| Validate{sort validation}
    Validate -->|NG| Err400[400 Bad Request]
    Validate -->|OK| QueryDB[Repository Layer]
    QueryDB --> CountQuery[Get COUNT]
    CountQuery --> ListQuery[Fetch Records<br/>LIMIT, OFFSET, ORDER BY]
    ListQuery --> Format[Format Response]
    Format --> Success[200 OK<br/>currentPage, totalCount, list]