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

TTTech LDAP API

The operations to manage LDAP users

TTTech LDAP API is one of 42 APIs that TTTech publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include LDAP. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 10 operations across 9 paths. It is described by OpenAPI 3.2.0, at version 3.1.0.

Requests are made against a single base URL, https://trynerve1.nerve.cloud.

10 operations 9 paths 0 schemas 3 GET1 PATCH5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.1.0
Base URL
https://trynerve1.nerve.cloud
Authentication
API Key, HTTP Basic, API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 4

TTTech LDAP API declares 4 security schemes for authenticating requests. An API key is passed in the header as sessionId (sessionId). It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as cookie (cookieAuth). It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 10

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

LDAP 10

The operations to manage LDAP users

GET
/nerve/ldap/active
Get status of LDAP configuration
get_ldap_status → 200400403404
POST
/nerve/ldap/connection/test
Test LDAP connection
test_ldap_connection body → 200400403404
GET
/nerve/ldap/default
Get default LDAP
get_default_ldap → 200204400403404
GET
/nerve/ldap
Retrieve LDAP configuration details
get_ldap_config_details → 200400403404
POST
/nerve/ldap
Create LDAP connections
create_ldap_connections body → 200400403404429
POST
/nerve/ldap/query/groups
LDAP server for groups with desired configuration
ldap_groups body → 200400403404429500
POST
/nerve/ldap/query/users
LDAP server for users with desired configuration
ldap_users body → 200400403404429500
PATCH
/nerve/ldap/{name}/active
Activate or deactivate LDAP
activate_deactivate_ldap 1 param body → 200400403404
PUT
/nerve/ldap/{file}
Update LDAP connections
update_ldap_connections 1 param body → 204400403404429
POST
/nerve/ldap/sync
Synchronization LDAP users
synchronize_ldap_users body → 200400403404429

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tttech-ldap-api-openapi.yml Raw ↑

Other APIs TTTech publishes across the network.

TTTech AUTH API
TTTech CAPABILITIES API
TTTech CODESYS PROCESS API
TTTech CONFIGURATION API
TTTech DATA EXCHANGE API
TTTech DATAPATH API
TTTech DNA API
TTTech DOCKER COMPOSE FILE API
TTTech DOCKER RESOURCES IMAGES API
TTTech DOCKER RESOURCES VOLUMES API
TTTech EMQX API
TTTech INITIALIZATION API
Where this information came from

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