> For the complete documentation index, see [llms.txt](https://docs.fraudcheck.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fraudcheck.co.za/product/products/verification/business/principal-details.md). # Principal details Returns a business's current and past directors. Retrieves the current and past directors of a business, including an archive of previous principals. Use it to build a complete picture of who controls, or has controlled, a company over time. {% hint style="info" %} Previously listed as *Business Principal Details*. {% endhint %} ## How it works Each request is checked against the commercial database using the company name or registration number you supply. Results can be retrieved again later. ## What it returns The business's current directors (name, ID number, date of birth, appointment date, director type and status), plus an archive of previous directors who have resigned or whose status has changed, in the same form. ## Inputs required A company name or registration number, and the reason for the enquiry. ## Data source Commercial business database. ## Consent and permissible purpose You must confirm on each request that consent has been obtained. See [Consent and permissible use](/product/overview/how-it-works/consent.md). ## Channels Portal and API. For request and response detail, see the [API reference](https://developer.fraudcheck.co.za/commercial-service/identity/principal-details). ## Outcomes The director record for the matched business. ## Turnaround Near real-time, typically under 5 seconds. ## When to use it Retrieving the full director list during KYB (know your business) checks, auditing changes in directorship over time, or cross-referencing directors against watchlists or adverse databases. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.fraudcheck.co.za/product/products/verification/business/principal-details.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.