hornet icon

hornet

Interact with hornet API

Actions452

LDAP Connection Settings → Service Dashboard Ldap Connections Post

AI-generated

Summary

Posts a request to the Hornet service dashboard to retrieve LDAP connection settings for a specified object, with pagination and sorting options.

Inputs

  • object_id (required) — The ID of an object (user, customer, or partner). Used as a query parameter to identify which object's LDAP connections to retrieve. Expected type is number (default 0). Sent as a query string parameter named 'object_id'.
  • APP-ID (required) — Application identifier issued by the service. Sent as a request header named 'APP-ID'. Expected type is string (default empty).
  • limit (required) — Maximum number of items per page for paginated results. Sent in the request body as a number (default 0).
  • page (required) — Zero‑based page index to fetch. Sent in the request body as a number (default 0).
  • key — Field name by which the results should be ordered. Sent in the request body as a string (default empty).
  • order — Sort direction, either 'asc' for ascending or 'desc' for descending. Sent in the request body as a string (default empty).
  • requestOptions — Advanced HTTP request settings that affect how the call is made (batching, SSL verification, proxy, timeout). These are node‑level options and are not sent to the API; they configure the underlying request execution. Includes sub‑options for batching (batch size and interval), allowing unauthorized certificates, proxy configuration, and request timeout.

Output shape

object

The operation returns the API response body from the Hornet service dashboard endpoint. This typically contains an array of LDAP connection objects matching the supplied filters, together with pagination metadata reflecting the limit, page, key, and order values supplied in the request.

Examples

Example 1: Fetch first 10 LDAP connections for object ID 123, sorted by name ascending.

Set object_id=123, limit=10, page=0, key='name', order='asc'. Provide a valid APP‑ID header.

Links

Discussion