How do I call the sessions endpoints over HTTP?
Table of Contents
- 1. Endpoints
- 1.1.
GET /api/v1/access/sessions - 1.2.
GET /api/v1/access/sessions/00000000-0000-0000-0000-000000000000 - 1.3.
POST /api/v1/access/sessions/get-many - 1.4.
POST /api/v1/access/sessions - 1.5.
PUT /api/v1/access/sessions - 1.6.
POST /api/v1/access/sessions/put-many - 1.7.
DELETE /api/v1/access/sessions/00000000-0000-0000-0000-000000000000 - 1.8.
POST /api/v1/access/sessions/delete-many
- 1.1.
This file documents the sessions resource over HTTP, one section per endpoint. Every section exports its own Hurl file into projects/ores.http/scripts/library/. Running a file sends that one request, so a failure names the endpoint it came from.
1. Endpoints
1.1. GET /api/v1/access/sessions
List sessions. It needs a session.
It forwards to iam.v1.sessions.list.
The request is:
GET /api/v1/access/sessions
GET {{base_url}}/api/v1/access/sessions
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.2. GET /api/v1/access/sessions/00000000-0000-0000-0000-000000000000
Get one session. It needs a session.
It forwards to iam.v1.sessions.get.
The request is:
GET /api/v1/access/sessions/00000000-0000-0000-0000-000000000000
GET {{base_url}}/api/v1/access/sessions/00000000-0000-0000-0000-000000000000
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.3. POST /api/v1/access/sessions/get-many
Get many sessions. It needs a session.
It forwards to iam.v1.sessions.get_many.
The request is:
POST /api/v1/access/sessions/get-many
POST {{base_url}}/api/v1/access/sessions/get-many
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.4. POST /api/v1/access/sessions
Create one session. It needs a session.
It forwards to iam.v1.sessions.put.
The request is:
POST /api/v1/access/sessions
POST {{base_url}}/api/v1/access/sessions
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.5. PUT /api/v1/access/sessions
Replace one session. It needs a session.
It forwards to iam.v1.sessions.put.
The request is:
PUT /api/v1/access/sessions
PUT {{base_url}}/api/v1/access/sessions
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.6. POST /api/v1/access/sessions/put-many
Write many sessions. It needs a session.
It forwards to iam.v1.sessions.put_many.
The request is:
POST /api/v1/access/sessions/put-many
POST {{base_url}}/api/v1/access/sessions/put-many
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.7. DELETE /api/v1/access/sessions/00000000-0000-0000-0000-000000000000
Delete one session. It needs a session.
It forwards to iam.v1.sessions.delete.
The request is:
DELETE /api/v1/access/sessions/00000000-0000-0000-0000-000000000000
DELETE {{base_url}}/api/v1/access/sessions/00000000-0000-0000-0000-000000000000
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200
1.8. POST /api/v1/access/sessions/delete-many
Delete many sessions. It needs a session.
It forwards to iam.v1.sessions.delete_many.
The request is:
POST /api/v1/access/sessions/delete-many
POST {{base_url}}/api/v1/access/sessions/delete-many
Accept: application/json
Authorization: Bearer {{token}}
HTTP 200