List logical connection bindings
Changed onLists logical usage bindings for physical connector instances. Logical bindings let one connector instance be safely reused across tenants, organization units, brands, legal entities, channels, and caller contexts while keeping discriminator, auth overlay, governance, and catalog projection metadata explicit.
Request
- Base URLhttps://api.example.com/api/connector/v1
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
Stable platform identifier for a configured connector instance.
Filter by the physical connector instance backing the logical binding.
Filter by organization unit in the logical context.
Filter by brand in the logical context.
Zero-based page index.
Page size.
Response
Paged logical connection bindings.
Example response
{
"data": [
{
"logicalConnectionBindingId": "brand-a-proof-vault",
"physicalConnectorInstanceId": "8a7f09af-7ac9-4d96-91f9-a2a252f4aa4b",
"logicalContext": {
"tenantId": "acme",
"organizationUnitId": "nl-ops",
"brandId": "brand-a"
}
}
],
"pagination": {
"limit": 20,
"offset": 0,
"page": 0,
"size": 20,
"total": 1,
"totalPages": 1,
"hasMore": false
}
}Changes
- info
the
////response's property pattern^sha256:[0-9a-f]{64}$was added for the status - info
the
////response's property pattern^sha256:[0-9a-f]{64}$was added for the status - info
the
////response's property pattern^sha256:[0-9a-f]{64}$was added for the status - info
the
////response's property pattern^sha256:[0-9a-f]{64}$was added for the status
- info