Documentation

{{docApp.title}}

{{docApp.description}}

Connect an AI assistant

Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.

The catalog did not load. Refresh the page to try again.

Loading…

How can we help?

{{docApp.searchError}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

 {{docApp.currentResultsSearchText}}  in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown. Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
  • {{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}

    {{resultItem.url}}

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

Entity API / getSupplierContacts

Operation Information

  • Application Reference: com.hornbill.suppliermanager
  • Scope: Entity - SupplierContacts
  • Class: Entity
  • Required Privilege Level: user
  • Required Rights: Group B - canViewSupplierContacts

Description

This flowcode operation gets details of all supplier contacts based on the search criteria provided.

Request Parameters

The getSupplierContacts API takes the following input parameters.

Note

When sending a JSON request payload to the API, the order of parameters is not significant. However, for XML request payloads, parameters must be provided in the exact order specified in this documentation to comply with input validation requirements.

Name Type Required Description
searchFilter xs:string No Search criteria for supplier contacts.
filterBySupplier xs:integer No Filters the results by supplier.
filterByStatus xs:string No Filters the results by supplier contact status. The values can be: "status.active", "status.archived", "all"
rowStart xs:integer Yes Row Start for Paging.
rowLimit xs:integer Yes Page Size.

Response Parameters

Name Type Description
outcome xs:string The outcome of the flowcode operation.
totalRecordCount xs:integer The total number of supplier contacts that match the search criteria.
supplierContacts xs:string A JSON string of supplier contacts.

Code Examples

In This Document