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 Visibility API

The Visibility API from Lokki — 12 operation(s) for visibility.

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

Tagged areas include Visibility. 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 12 operations across 12 paths, and defines 35 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.

12 operations 12 paths 35 schemas 3 GET9 POST

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 Visibility 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 12

Across 12 paths, the API surfaces 12 operations — 3 GET, 9 POST. Each is listed below with its method, path, parameters, and response codes.

Visibility 12
POST
/v2/visibility/signup-form
sendVisibilitySignupForm body → 200201
POST
/v2/visibility/user
createVisibilityUser body → 201
POST
/v2/visibility/user/setup
setupVisibilityUser body → 200201
POST
/v2/visibility/user/validation-code/send
sendVisibilityValidationCode body → 201
POST
/v2/visibility/user/validation-code/check
checkVisibilityValidationCode body → 201
GET
/v2/visibility/my-data
getVisibilityData → 200
POST
/v2/visibility/upgrade/form
sendVisibilityUpgradeForm body → 201
POST
/v2/visibility/upgrade/help-request
sendVisibilityHelpRequest body → 201
POST
/v2/visibility/stripe/setup
setupVisibilityStripeAccount body → 201
GET
/v2/visibility/stripe/check
checkVisibilityStripeSetupStatus → 200
GET
/v2/visibility/onboarding/check
checkVisibilityOnboardingStatus → 200
POST
/v2/visibility/products
createOneVisibilityProduct body → 201

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are Service (27 properties), CreateUpdateServiceDto (24 properties), VisibilityUpgradeFormInfosDto (18 properties), VisibilityCompanyData (18 properties). Each schema is shown below with its type and property counts.

CompanyDocumentBodyDto
object
4 properties 4 required
UserValidationCode
object
2 properties 2 required
CreateUpdateServiceDto
object
24 properties 20 required
PriceModelLLDDuration
object
6 properties 6 required
AttachedFile
object
5 properties 4 required
SendVisibilityValidationCodeDto
object
2 properties 2 required
ItemAttribute
object
2 properties 2 required
PriceModelRangeDuration
object
8 properties 7 required
VisibilitySetupUserDto
object
2 properties 2 required
ServiceTag
object
2 properties 2 required
StripeAccountUrlDto
object
1 property 1 required
TentativeCategorization
object
2 properties 2 required
VisibilityUpgradeFormInfosDto
object
18 properties 16 required
CheckStripeSetupStatusReturnDto
object
2 properties 2 required
SelfTestUtmInfos
object
11 properties
ServiceField
object
4 properties 4 required
VisibilityFormExternalCompanyDto
object
4 properties 4 required
VisibilityCreateUserDto
object
4 properties 3 required
PriceModelSpecificDuration
object
6 properties 6 required
VisibilityHelpRequestDto
object
3 properties 3 required
CheckOnboardingStatusReturnDto
object
2 properties 2 required
VisibilityCompleteFormInfosDto
object
10 properties 10 required
VisibilityCompanyData
object
18 properties 17 required
VisibilitySetupUserResultDto
object
2 properties 2 required
CreateUpdateExternalCompanyAddressComponentsDto
object
8 properties 7 required
VisibilitySetupStripeDto
object
2 properties 1 required
ExternalCompanyAddressComponents
object
8 properties 7 required
LocalizedContent
object
CheckValidationCodeStatusReturnDto
object
1 property 1 required
CheckVisibilityValidationCodeDto
object
2 properties 2 required
ItemOnlineStoreInformation
object
2 properties 2 required
ServiceAttribute
object
2 properties 2 required
User
object
16 properties 12 required
Service
object
27 properties 23 required
VisibilityCreateAccountResultDto
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lokki-visibility-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 Visibility 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.