Skip to main content

Design Requests Overview

Manage design requests, priorities, states, and associated tasks for tracking design workflows.

List Design Requests

Retrieve all design requests with related data.
GET /design/request

Authentication

Authorization
string
required
Valid session or Sanctum token

Response

Returns Inertia view with:
requests
array
All design requests
priorities
array
Available priority levels
time_states
array
Time state options
states
array
Design request states
designers
array
Users with type=‘designer’
customers
array
Customer list grouped by type (local/external)
sellers
array
Available sellers

Create Design Request

Create a new design request.
POST /design/request

Request Body

priority_id
integer
required
Priority level ID
designer_id
integer
required
Designer user ID
seller_document
string
required
Seller document number
customer_id
string
required
Customer ID/document
comments
string
Design request comments
reception_date
date
required
Date request was received
tentative_date
date
Tentative completion date
real_date
date
Actual completion date
delivery_date
date
Delivery date to customer
customer_approved_date
date
Date customer approved design
estimated_arrival_sherpa_date
date
Estimated arrival date for Sherpa
time_state_id
integer
required
Time state ID
state_id
integer
required
Design state ID
observations
string
Additional observations

Example Request

curl -X POST https://your-domain.com/design/request \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "priority_id": 1,
    "designer_id": 5,
    "seller_document": "123456789",
    "customer_id": "987654321",
    "comments": "Client needs custom logo design",
    "reception_date": "2026-03-01",
    "tentative_date": "2026-03-10",
    "time_state_id": 1,
    "state_id": 1,
    "observations": "High priority client"
  }'

Response

Returns array of all design requests including newly created (200 status).

Get Design Request Details

Retrieve detailed information about a specific design request.
GET /design/request/{id}

Path Parameters

id
integer
required
Design request ID

Response

Returns Inertia view with:
design_request
object
Complete design request object
priorities
array
Available priorities
time_states
array
Available time states
states
array
Available states
designers
array
Designer users
customers
array
Customer list
sellers
array
Seller list

Update Design Request

Update an existing design request.
PUT /design/request/{id}
The current implementation only updates the name field. This may be expanded in the future.

Path Parameters

id
integer
required
Design request ID

Request Body

name
string
required
Updated request name

Example Request

curl -X PUT https://your-domain.com/design/request/5 \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Updated Design Request Name"
  }'

Response

Returns array of all design requests with updates (200 status).

Update Design Request State

Update a specific state property of a design request.
POST /design/request/update-state

Request Body

id
integer
required
Design request ID
property
string
required
Property name to update (e.g., ‘state_id’, ‘time_state_id’)
state_id
integer
required
New state value

Example Request

curl -X POST https://your-domain.com/design/request/update-state \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 5,
    "property": "state_id",
    "state_id": 3
  }'

Response

Returns the updated design request object (200 status).
{
  "id": 5,
  "priority_id": 1,
  "designer_id": 5,
  "seller_document": "123456789",
  "customer_id": "987654321",
  "state_id": 3,
  "time_state_id": 1,
  "reception_date": "2026-03-01",
  "created_at": "2026-03-01 10:00:00",
  "updated_at": "2026-03-04 11:15:00"
}

Delete Design Request

Delete a design request.
DELETE /design/request/{id}

Path Parameters

id
integer
required
Design request ID to delete

Example Request

curl -X DELETE https://your-domain.com/design/request/5 \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Accept: application/json"

Response

Returns array of remaining design requests (200 status).

Design Priorities

List Priorities

GET /design/priority

Create Priority

POST /design/priority

Update Priority

PUT /design/priority/{id}

Delete Priority

DELETE /design/priority/{id}

Design States

List States

GET /design/state

Create State

POST /design/state

Update State

PUT /design/state/{id}

Delete State

DELETE /design/state/{id}

Design Time States

List Time States

GET /design/time-state

Create Time State

POST /design/time-state

Update Time State

PUT /design/time-state/{id}

Delete Time State

DELETE /design/time-state/{id}

Design Tasks

Create Task

POST /design/task

Update Task

PUT /design/task/{id}

Delete Task

DELETE /design/task/{request_id}/{id}
request_id
integer
required
Design request ID
id
integer
required
Task ID

Error Responses

500 Internal Server Error

{
  "message": "Error details from exception"
}

Implementation Notes

Source: app/Http/Controllers/DesignRequestController.php

Customer Data Source

Customers are retrieved from two sources:
  1. Local: From GBapp.dbo.users where type=‘customer’
  2. External: From external database connection ‘ssf’ (un_tercegener table)
Customers are grouped by type in the response.

Build docs developers (and LLMs) love