LEAP-Systems / LEAP-Systems/api
Sessions
@ztnel is already working on this.
Since Jul 30, 2021.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description
Endpoint
GET /v1/session/<id>
This resource is generated by the backend automatically on a capture without a session in the header. After the resource is created the session id is returned to the client so all subsequent captures can be linked with a session
PUT /v1/session/<id>
Used by the backend to append new captures to a session
DELETE /v1/session/<id>
removes a session instance
Model
Sessions will consist of a list of captures in the order they were taken. Only calibration-related captures are recorded by the backend.
{
"id": "dsajdksbadjba",
"created_at": "2021-07-11",
"updated_at": "2021-07-11",
"captures": [
"jljfkdljsfkld",
"dasbyduisadvu",
"kldsjdaidoahd",
"jljfkdljsfkld"
]
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.