> ## Documentation Index > Fetch the complete documentation index at: https://integration.delogue.com/llms.txt > Use this file to discover all available pages before exploring further. # Get supplier connection counts > Returns the number of active supplier connections and pending connection requests for the current designer organization. The active count spans every direct-supplier relationship and is available to any designer user. The pending count is the number of open connection requests awaiting a response. Viewing the pending count requires permission to view pending connections. Callers without that permission still receive the active count, with the pending count returned as zero. ## OpenAPI ````yaml https://service.my.delogue.com/openapi/external.json get /api/suppliers/counts openapi: 3.1.1 info: title: Delogue External API - (Production) description: Integration endpoints for Delogue API version: 1.0.0 servers: - url: / description: The Delogue environment serving this document. - url: https://{host} description: Per-customer Delogue API host. variables: host: default: service.my.delogue.com description: >- The API host for your Delogue environment, e.g. service..delogue.com. security: [] tags: - name: Barcodes - name: Brands - name: CareInstructionIcons - name: CareInstructionLayers - name: CareInstructionMaterials - name: CareInstructions - name: Color Groups - name: Colors - name: ComplianceCategories - name: ComplianceCustomFields - name: Facilities - name: Groups - name: ItemCategories - name: Items - name: MeasurementCharts - name: MigrationApproval - name: MigrationVerification - name: OrganizationMigration - name: Organizations - name: SampleRequests - name: SampleTypes - name: Seasons - name: SizeRanges - name: Style Prices - name: StyleCareInstructions - name: StyleCategories - name: StyleColors - name: StyleContacts - name: StyleCustomFields - name: StyleFiles - name: StyleItems - name: StyleRelations - name: Styles - name: StyleSkus - name: StyleSupplierFacilities - name: SubSuppliers - name: Suppliers paths: /api/suppliers/counts: get: tags: - Suppliers summary: Get supplier connection counts description: >- Returns the number of active supplier connections and pending connection requests for the current designer organization. The active count spans every direct-supplier relationship and is available to any designer user. The pending count is the number of open connection requests awaiting a response. Viewing the pending count requires permission to view pending connections. Callers without that permission still receive the active count, with the pending count returned as zero. operationId: Suppliers_GetCounts responses: '200': description: OK content: text/plain: schema: $ref: '#/components/schemas/ApiResponseOfSupplierConnectionCountsDto' application/json: schema: $ref: '#/components/schemas/ApiResponseOfSupplierConnectionCountsDto' text/json: schema: $ref: '#/components/schemas/ApiResponseOfSupplierConnectionCountsDto' '401': description: Unauthorized content: application/problem+json: schema: $ref: '#/components/schemas/ApiErrorResponse' '403': description: Forbidden content: text/plain: schema: $ref: '#/components/schemas/ApiErrorResponse' application/json: schema: $ref: '#/components/schemas/ApiErrorResponse' text/json: schema: $ref: '#/components/schemas/ApiErrorResponse' '500': description: Internal Server Error content: application/problem+json: schema: $ref: '#/components/schemas/ApiErrorResponse' security: - {} components: schemas: ApiResponseOfSupplierConnectionCountsDto: required: - status - code - data type: object properties: status: $ref: '#/components/schemas/ApiResponseStatus' description: >- The coarse outcome of the request, indicating whether it succeeded or failed. code: type: string description: >- The specific machine-readable outcome code, such as ok on success or the most specific error code on failure. Always lowercase on the wire. data: oneOf: - type: 'null' - $ref: '#/components/schemas/SupplierConnectionCountsDto' description: >- The response payload, either a single object for a by-id read or an array for a bulk operation. Omitted from the body when there is no value. description: >- The response payload, either a single object for a by-id read or an array for a bulk operation. Omitted from the body when there is no value. additionalProperties: false ApiErrorResponse: type: object properties: status: $ref: '#/components/schemas/ApiResponseStatus' description: >- The coarse outcome of the request, indicating whether it succeeded or failed. code: type: string description: >- The specific machine-readable outcome code, such as ok on success or the most specific error code on failure. Always lowercase on the wire. error: $ref: '#/components/schemas/ErrorWrapper' description: >- The error payload, present instead of data on a failed response. It wraps the list of detail rows describing what went wrong. additionalProperties: false ApiResponseStatus: enum: - success - error type: string description: >- The coarse outcome of the request, indicating whether it succeeded or failed. SupplierConnectionCountsDto: type: object properties: activeConnectionsCount: pattern: ^-?(?:0|[1-9]\d*)$ type: - integer - string description: >- Number of active direct-supplier connections for the current designer organization, counting every supplier relationship regardless of its connection status. format: int32 pendingConnectionsCount: pattern: ^-?(?:0|[1-9]\d*)$ type: - integer - string description: >- Number of open supplier connection requests awaiting a response for the current designer organization. Returned as zero for callers without permission to view pending connections. format: int32 additionalProperties: false description: >- The response payload, either a single object for a by-id read or an array for a bulk operation. Omitted from the body when there is no value. ErrorWrapper: type: object properties: details: type: array items: $ref: '#/components/schemas/ErrorDetailDto' description: >- The list of individual error detail rows for this failure, one per field or rule that failed. additionalProperties: false description: >- The error payload, present instead of data on a failed response. It wraps the list of detail rows describing what went wrong. ErrorDetailDto: required: - type - field - value type: object properties: type: type: string description: >- The hierarchical error code identifying the specific failure, such as validation_error.required_field. Consumers branch on this rather than on the message text. field: type: - 'null' - string description: >- The input field that caused the failure. Omitted when no specific field is at fault, such as an authorization denial or a server error. value: type: - 'null' - string description: >- A human-readable message describing the failure, or the offending value or limit that triggered it. additionalProperties: false ````