Skip to main content

Suppliers

Entity›Relationship›Relationship.Organization.Supplier

A Supplier relationship links your own Organisation (parent) to another Organisation (child), defining that organisation as a supplier to your business. It stores supplier-specific data such as payment terms, price list, and mailing preferences.

Use the Relationship_Organization_Supplier endpoint to manage your suppliers. Suppliers inherit all fields from Relationship and add supplier-specific fields.

Not to be confused with "Organisations"

A Supplier (Relationship_Organization_Supplier) is a Relationship — it defines the role an organisation plays as a vendor to your business. An Organisation (Relation_Organization) is the entity itself — the company record. The same Organisation can be both a Supplier and a Customer.

Endpoints​

List Suppliers​

Retrieve a paginated list of suppliers.

GET/v1/odata/Relationship_Organization_Supplier

Single Supplier​

Retrieve a single supplier by its ID.

GET/v1/odata/Relationship_Organization_Supplier({id})

With expanded relations:

GET/v1/odata/Relationship_Organization_Supplier({id})?$expand=Organization,Relation

Create Supplier with a New Organisation​

Create a supplier relationship and its underlying Organisation in one call:

POST/v1/odata/Relationship_Organization_Supplier
  • Relation.ID — Your own organisation (parent)
  • Organization — The supplier Organisation fields (created automatically)

Create Supplier from an Existing Organisation​

Link an existing Organisation as a supplier:

POST/v1/odata/Relationship_Organization_Supplier

Update Supplier​

Update an existing supplier relationship. Provide only the fields to update.

PUT/v1/odata/Relationship_Organization_Supplier({id})

Delete Supplier​

Delete a supplier relationship by ID. This removes the supplier role but does not delete the underlying Organisation.

DELETE/v1/odata/Relationship_Organization_Supplier({id})
warning

Make sure you do not orphan the Organisation when deleting a Supplier relationship. If it is the only relationship linking that Organisation to your network, consider deleting the Organisation instead.

Fields​

Standard Fields (all entities)​

FieldTypeDescription
IDGuidPrimary key (UUID)
_TypeStringEntity type discriminator (Relationship.Organization.Supplier)
_NameStringComputed display name
SortIndexDoubleSorting order
CreationDateDateTimeOffsetDate the record was created
LastMutationDateDateTimeOffsetDate of the last modification
IsActiveBooleanWhether the record is active
IsClosedBooleanWhether the record is closed

Supplier Fields​

FieldTypeDescription
NameStringSupplier display name
PaymentTermInDaysDoublePayment term in days

Relationships​

RelationshipTarget EntityCardinalityDescription
RelationRelationN:1Parent organisation (your company)
OrganizationRelation.OrganizationN:1The supplier organisation
PriceListPriceListN:1Assigned price list

Expanding Relationships​

GET/v1/odata/Relationship_Organization_Supplier({id})?$expand=Organization
GET/v1/odata/Relationship_Organization_Supplier?$expand=Organization,Relation
GET/v1/odata/Relationship_Organization_Supplier({id})/Relation

Filtering Examples​

GET/v1/odata/Relationship_Organization_Supplier?$filter=contains(Name, '{Name}')&$top={top}
GET/v1/odata/Relationship_Organization_Supplier?$filter=PaymentTermInDays eq {PaymentTermInDays}&$top={top}
GET/v1/odata/Relationship_Organization_Supplier?$filter=CreationDate gt {CreationDate}&$top={top}
GET/v1/odata/Relationship_Organization_Supplier?$filter=IsClosed eq {IsClosed}&$top={top}

Custom Query​

Build your own OData query against Relationship_Organization_Supplier. Open Run and edit the whole request inline — swap the entity set, change the $filter, or add $expand, $select, $orderby, $top, $skip. Type $ for suggestions; use ↺ Reset to restore this example.

GET/v1/odata/Relationship_Organization_Supplier?$top=10