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

Screenleap Screen Shares API

Create, retrieve, list and stop screen share sessions.

Screenleap Screen Shares API is published by Screenleap on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Screen Shares. 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 5 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.0.3, at version 2.0.

Requests are made against a single base URL, https://api.screenleap.com/v2.

5 operations 4 paths 3 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0
Base URL
https://api.screenleap.com/v2
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Screenleap Screen Shares API declares 2 security schemes for authenticating requests. An API key is passed in the header as accountid (accountId). An API key is passed in the header as authtoken (authToken). By default, every request must be authenticated.

  • accountId — Your Screenleap account identifier.
  • authToken — Your Screenleap authentication token. SSL required when sending it.

Paths & Operations 5

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

Screen Shares 5

Create, retrieve, list and stop screen share sessions.

POST
/screen-shares
Create a screen share session
createScreenShare → 200401
GET
/screen-shares
Retrieve share sessions
listScreenShares 6 params → 200401
GET
/screen-shares/{screenShareCode}
Retrieve share session information
getScreenShare 1 param → 200401403404
POST
/screen-shares/{screenShareCode}/stop
Stop an active share session
stopScreenShare 1 param → 200401403404
GET
/recent-screen-shares
Retrieve recent share sessions
listRecentScreenShares → 200401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are ScreenShare (15 properties), Participant (7 properties), CreatedScreenShare (2 properties). Each schema is shown below with its type and property counts.

Participant
object
A participant (presenter or viewer) in a screen share session.
7 properties
ScreenShare
object
A screen share session.
15 properties
CreatedScreenShare
object
Response returned when a screen share session is created.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

screenleap-screen-shares-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Screenleap Screen Shares 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.