How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Lokki Session Event API

The Session Event API from Lokki — 20 operation(s) for session event.

Lokki Session Event API is one of 97 APIs that Lokki publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Session Event. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 21 operations across 20 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against the base URL https://prod.api.eu-west-3.lokki.rent.

21 operations 20 paths 31 schemas 2 DELETE13 GET3 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://prod.api.eu-west-3.lokki.rent
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Lokki Session Event API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-access-token (x-access-token). By default, every request must be authenticated.

Paths & Operations 21

Across 20 paths, the API surfaces 21 operations — 2 DELETE, 13 GET, 3 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Session Event 21
POST
/v2/session-event/createEvent
createEvent body → 201
POST
/v2/session-event/duplicate/{eventId}
duplicateEvent 1 param → 201
PUT
/v2/session-event/event/{eventId}
updateEvent 1 param body → 200
GET
/v2/session-event/event/{eventId}
getEvent 1 param → 200
DELETE
/v2/session-event/delete-event/{eventId}
deleteEvent 1 param → 200
GET
/v2/session-event/onlineStoreEvent/{companyId}/{eventId}
getOnlineStoreEvent 4 params → 200
GET
/v2/session-event/events
getEvents → 200
POST
/v2/session-event/createSession
createSession body → 201
PUT
/v2/session-event/check-update-session-time/{sessionId}
checkUpdateSessionTime 1 param body → 200
PUT
/v2/session-event/updateSession/{sessionId}
updateSession 1 param body → 200
DELETE
/v2/session-event/deleteSession/{sessionId}/{eventId}
deleteSession 2 params → 200
GET
/v2/session-event/getUpcomingSessions/{page}
getUpcomingSessions 3 params → 200
GET
/v2/session-event/getUpcomingSessions
getAllUpcomingSessions 2 params → 200
GET
/v2/session-event/getSession/{sessionId}
getSession 1 param → 200
GET
/v2/session-event/getSessionStartDateGte/{eventId}/{startDate}
getSessionStartDateGte 2 params → 200
GET
/v2/session-event/getAvailableSessions/{eventId}
getAvailableSessions 1 param → 200
GET
/v2/session-event/sessionAvailableProducts/{sessionId}/{orderEventId}
getSessionAvailableProducts 2 params → 200
GET
/v2/session-event/onlineStoreSessionAvailableProducts/{companyId}/{sessionId}
getOnlineStoreSessionAvailableProducts 2 params → 200
GET
/v2/session-event/getEnrichedSessionsPagination/{eventId}
getEnrichedSessionsPagination 3 params → 200
GET
/v2/session-event/getEventOrderInfo/{eventId}
getEventOrderInfo 1 param → 200
GET
/v2/session-event/firstAvailableSessionDate/{companyId}/{eventId}
getFirstAvailableSessionDate 2 params → 200

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are Event (17 properties), EventOnlineStore (16 properties), CreateUpdateEventDto (15 properties), EnrichedSession (9 properties). Each schema is shown below with its type and property counts.

SessionRecurring
object
6 properties 6 required
EventOrderInfoDto
object
7 properties 7 required
CreateUpdateEventOptionDto
object
3 properties 3 required
AvailableItemEvent
object
5 properties 5 required
AvailableSessionEventDto
object
9 properties 9 required
UpcomingSessionPaginationDto
object
2 properties 2 required
EventOption
object
3 properties 3 required
EnrichedSession
object
9 properties 9 required
EnrichedSessionsPaginationDto
object
2 properties 2 required
Category
object
3 properties 3 required
CreateUpdateSessionEventDto
object
3 properties 2 required
SessionEvent
object
8 properties 8 required
SessionEventOnlineStore
object
6 properties 6 required
AvailableProductEvent
object
8 properties 8 required
CreateUpdateEventCategoryDto
object
3 properties 3 required
GetFirstAvailableSessionResponseDto
object
1 property 1 required
CreateUpdateEventPricingDto
object
3 properties 3 required
AvailableCategoryEvent
object
5 properties 5 required
CheckSessionEventUpdateTimeUnavailability
object
2 properties 2 required
CreateUpdateEventItemDto
object
3 properties 3 required
TagValue
object
4 properties 3 required
LocalizedContent
object
Event
object
17 properties 17 required
NotAvailableRange
object
2 properties 2 required
CreateUpdateEventSessionEventDto
object
7 properties 6 required
UpcomingSessionEventDto
object
9 properties 9 required
Pricing
object
3 properties 3 required
EventOnlineStore
object
16 properties 16 required
CreateUpdateEventDto
object
15 properties 15 required
Item
object
3 properties 3 required
AvailableOptionEvent
object
8 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lokki-session-event-api-openapi.yml Raw ↑

Other APIs Lokki publishes across the network.

Lokki Action Log API
Lokki Admin API
Lokki Ahrefs API
Lokki Ancv API
Lokki Api Key API
Lokki Api Key V2 API
Lokki Auth API
Lokki Aws S3 API
Lokki Bookings API
Lokki Business Registry API
Lokki Cart Suggestion API
Lokki Catalogue API
Where this information came from

This is an independent, third-party profile of Lokki Session Event API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.