> For the complete documentation index, see [llms.txt](https://docs.unimarket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unimarket.com/api-reference/suppliers/object.md).

# The Supplier Object

The Supplier object and its attributes

A Supplier represents a vendor registered in the Nova platform. Depending on the endpoint, you will receive either a `SupplierSummary` (in list responses) or a `SupplierDetail` (when fetching a single supplier).

## Key concepts

**SupplierSummary vs SupplierDetail** — List endpoints return a lightweight `SupplierSummary` with core identity fields. Fetching a single supplier returns the full `SupplierDetail`, which includes contacts, remittance addresses, bank accounts, and payment terms. Only fetch detail when you need it.

**profileType** — Determines whether the supplier is a business entity or an individual person. This affects which tax identification types are applicable.

**taxIdentificationType** — The type of tax ID registered for the supplier. Values vary by region and entity type. See the schema reference below for all allowed values.

**paymentTerms** — Agreed payment terms between your organisation and the supplier (e.g. `NET30`). Used for accounts payable processing.

## Schema reference

For the full auto-rendered schema including all fields and types, see the **Models** section in the sidebar.


---

# 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.unimarket.com/api-reference/suppliers/object.md?ask=<question>&goal=<user_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.