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

Viridi Admin Controller API

The admin-controller API from Viridi — 18 operation(s) for admin-controller.

Viridi Admin Controller API is one of 56 APIs that Viridi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include admin-controller. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 24 operations across 18 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 3.7.0.

Requests are made against a single base URL, https://vista.viridiparente.com.

24 operations 18 paths 21 schemas 2 DELETE14 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.7.0
Base URL
https://vista.viridiparente.com
Authentication
HTTP Loginpassword
Resource Areas
1

Authentication & Security 1

Viridi Admin Controller API declares 1 security scheme for authenticating requests. It uses HTTP loginpassword authentication (HTTP_login_form).

  • HTTP_login_form — Enter Username / Password

Paths & Operations 24

Across 18 paths, the API surfaces 24 operations — 2 DELETE, 14 GET, 8 POST. Each is listed below with its method, path, parameters, and response codes.

admin-controller 24
POST
/api/admin/settings
Get the Administration Settings object using key (getAdminSettings)
saveAdminSettings body → 200
POST
/api/admin/settings/testSms
Send test sms (sendTestMail)
sendTestSms body → 200
POST
/api/admin/settings/testMail
Send test email (sendTestMail)
sendTestMail body → 200
GET
/api/admin/securitySettings
Get the Security Settings object
getSecuritySettings → 200
POST
/api/admin/securitySettings
Update Security Settings (saveSecuritySettings)
saveSecuritySettings body → 200
GET
/api/admin/repositorySettings
Get repository settings (getRepositorySettings)
getRepositorySettings → 200
POST
/api/admin/repositorySettings
Creates or Updates the repository settings (saveRepositorySettings)
saveRepositorySettings body → 200
DELETE
/api/admin/repositorySettings
Delete repository settings (deleteRepositorySettings)
deleteRepositorySettings → 200
POST
/api/admin/repositorySettings/checkAccess
Check repository access (checkRepositoryAccess)
checkRepositoryAccess body → 200
GET
/api/admin/jwtSettings
Get the JWT Settings object (getJwtSettings)
getJwtSettings → 200
POST
/api/admin/jwtSettings
Update JWT Settings (saveJwtSettings)
saveJwtSettings body → 200
GET
/api/admin/autoCommitSettings
Get auto commit settings (getAutoCommitSettings)
getAutoCommitSettings → 200
POST
/api/admin/autoCommitSettings
Creates or Updates the auto commit settings (saveAutoCommitSettings)
saveAutoCommitSettings body → 200
DELETE
/api/admin/autoCommitSettings
Delete auto commit settings (deleteAutoCommitSettings)
deleteAutoCommitSettings → 200
GET
/api/admin/updates
Check for new Platform Releases (checkUpdates)
checkUpdates → 200
GET
/api/admin/systemInfo
Get system info (getSystemInfo)
getSystemInfo → 200
GET
/api/admin/settings/{key}
Get the Administration Settings object using key (getAdminSettings)
getAdminSettings 1 param → 200
GET
/api/admin/repositorySettings/info
Get repository settings info
getRepositorySettingsInfo → 200
GET
/api/admin/repositorySettings/exists
Check repository settings exists (repositorySettingsExists)
repositorySettingsExists → 200
GET
/api/admin/mail/oauth2/loginProcessingUrl
Get OAuth2 log in processing URL (getMailProcessingUrl)
getMailProcessingUrl → 200
GET
/api/admin/mail/oauth2/code
Code processing url
codeProcessingUrl 2 params → 200
GET
/api/admin/mail/oauth2/authorize
Redirect user to mail provider login page
getAuthorizationUrl → 200
GET
/api/admin/featuresInfo
Get features info (getFeaturesInfo)
getFeaturesInfo → 200
GET
/api/admin/autoCommitSettings/exists
Check auto commit settings exists (autoCommitSettingsExists)
autoCommitSettingsExists → 200

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are UserPasswordPolicy (10 properties), RepositorySettings (10 properties), SystemInfoData (8 properties), UpdateMessage (6 properties). Each schema is shown below with its type and property counts.

AdminSettings
object
A JSON value representing the Mail Settings.
5 properties
TwilioSmsProviderConfiguration
AdminSettingsId
object
1 property 1 required
UpdateMessage
object
6 properties
FeaturesInfo
object
5 properties
AwsSnsSmsProviderConfiguration
TenantId
object
2 properties 2 required
AutoVersionCreateConfig
object
4 properties
RepositorySettingsInfo
object
2 properties
SystemInfoData
object
8 properties
SmsProviderConfiguration
object
1 property 1 required
UserPasswordPolicy
object
10 properties
SystemInfo
object
2 properties
JwtPair
object
JWT Pair
3 properties
JsonNode
A value representing the any type (object or primitive)
SecuritySettings
object
A JSON value representing the Security Settings.
4 properties
AutoCommitSettings
object
SmppSmsProviderConfiguration
5 required
RepositorySettings
object
A JSON value representing the Repository Settings.
10 properties
JwtSettings
object
A JSON value representing the JWT Settings.
4 properties
TestSmsRequest
object
A JSON value representing the Test SMS request.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

viridi-parente-admin-controller-api-openapi.yml Raw ↑

Other APIs Viridi publishes across the network.

Viridi Alarm Comment Controller API
Viridi Alarm Controller API
Viridi Asset Controller API
Viridi Asset Profile Controller API
Viridi Audit Log Controller API
Viridi Auth Controller API
Viridi Cbrs Controller API
Viridi Component Descriptor Controller API
Viridi Customer Controller API
Viridi Dashboard Controller API
Viridi Device Connectivity Controller API
Viridi Device Controller API
Where this information came from

This is an independent, third-party profile of Viridi Admin Controller 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.