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

SafeLine Websites API

Protected website (application) management

SafeLine Websites API is one of 9 APIs that SafeLine publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Websites. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, and a GitHub repository.

This API exposes 5 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version 2.0.0.

Requests are made against a single base URL, https://{host}:9443.

5 operations 2 paths 6 schemas 1 DELETE1 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0.0
Server
https://{host}:9443
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

SafeLine Websites API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-SLCE-API-Token (APITokenAuth). By default, every request must be authenticated.

  • APITokenAuth — API token obtained from the SafeLine management interface

Paths & Operations 5

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

Websites 5

Protected website (application) management

GET
/api/SoftwareReverseProxyWebsiteAPI
List Protected Websites
listWebsites 2 params → 200
POST
/api/SoftwareReverseProxyWebsiteAPI
Create Protected Website
createWebsite body → 200
PUT
/api/SoftwareReverseProxyWebsiteAPI
Update Protected Website
updateWebsite body → 200
DELETE
/api/SoftwareReverseProxyWebsiteAPI
Delete Protected Website
deleteWebsite body → 200
POST
/api/EnableDisableWebsiteAPI
Enable or Disable Website Protection
toggleWebsiteProtection body → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Website (9 properties), UpdateWebsiteRequest (7 properties), CreateWebsiteRequest (6 properties), WebsiteResponse (3 properties). Each schema is shown below with its type and property counts.

CreateWebsiteRequest
object
6 properties 3 required
SuccessResponse
object
3 properties
WebsiteListResponse
object
3 properties
Website
object
9 properties
UpdateWebsiteRequest
object
7 properties 1 required
WebsiteResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

safeline-websites-api-openapi.yml Raw ↑

Other APIs SafeLine publishes across the network.

SafeLine MCP Server
SafeLine ACL Rules API
SafeLine Authentication API
SafeLine Reports API
SafeLine Security Policies API
SafeLine SSL Certificates API
SafeLine System API
SafeLine Users API
Where this information came from

This is an independent, third-party profile of SafeLine Websites 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.