[BUG] API and documentation are inconsistent: Created Time (created_at) is not returned by the current share API.

[bywenshu]

Please confirm the following

• I have read and agree to AGPL-3.0 Section 15 .
  The program is provided "as is" without any warranties; you bear all risks of using it.

• I have read and agree to AGPL-3.0 Section 16 .
  The copyright holders and distributors are not liable for any damages resulting from the use or inability to use the program.

• I confirm my description is clear, polite, helps developers quickly locate the issue, and complies with community rules.

• I have read the OpenList documentation.

• I confirm there are no duplicate issues or discussions.

• I confirm this is an OpenList issue, not caused by other reasons (such as network, dependencies, or operation).

• I believe this issue must be handled by OpenList and not by a third party.

• I confirm this issue is not fixed in the latest version.

• I have not read these checkboxes and therefore I just ticked them all, Please close this issue.

OpenList Version (required)

v4.1.10

Storage Driver Used (required)

Local Storage

Bug Description (required)

The page at https://fox.oplist.org/364155755e0 indicates that the API returns the share creation time, namely the created_at field. However, in practice, the API does not return this field, which is inconsistent with the documentation.

Logs (required)

Raw JSON:
{
"accessed": 0,
"creator": "test",
"creator_role": 0,
"disabled": false,
"expires": null,
"extract_folder": "",
"files": [
"/PATH/to/FILE.ext"
],
"header": "",
"id": "4qhopv11",
"max_accessed": 0,
"order_by": "",
"order_direction": "",
"pwd": "",
"readme": "",
"remark": ""
}

Configuration File Content (required)

{"id":1,"mount_path":"/HDD","order":0,"driver":"Local","cache_expiration":0,"custom_cache_policies":"","status":"work","addition":"{"root_folder_path":"/HDD","directory_size":true,"thumbnail":true,"thumb_cache_folder":"/HDD/Cache","thumb_concurrency":"16","video_thumb_pos":"20%","show_hidden":true,"mkdir_perm":"777","recycle_bin_path":"delete permanently"}","remark":"","modified":"2025-12-22T21:59:37.052401892+08:00","disabled":false,"disable_index":false,"enable_sign":false,"order_by":"name","order_direction":"asc","extract_folder":"front","web_proxy":false,"webdav_policy":"native_proxy","proxy_range":false,"down_proxy_url":"","disable_proxy_sign":false}

Reproduction Link (optional)

No response

[jyxjjj]

Full curl required

[bywenshu]

curl -k -sS --location --request GET 'https://<OPENLIST_HOST>/api/share/get?id=<SHARE_ID>' \
  --header 'Authorization: <JWT_TOKEN>'

{"code":200,"message":"success","data":{"id":"<SHARE_ID>","expires":null,"pwd":"","accessed":0,"max_accessed":1,"disabled":false,"remark":"issue-2311-curl-test-<TIMESTAMP>","readme":"","header":"","order_by":"","order_direction":"","extract_folder":"","files":["/<REDACTED_PATH>/curl_test.txt"],"creator":"<USERNAME>","creator_role":0}}

So this looks reproducible on v4.1.10. The current docs example for /api/share/list appears stale: it shows path, expiration, and created_at, while the actual response uses fields such as files and expires, and does not include a creation-time field.

[jyxjjj]

@dezhishen Do you think this is a doc issue or a backend issue?
CC @KirCute — sorry to bother you, could you share your first impression?

[KirCute]

This is a doc issue. The database does not store the creation time of the share, only the creator and expiration time, and it does not return the creation time to the front-end.