SupplierOffice
Questi contenuti non sono ancora disponibili nella tua lingua.
Manage supplier-office associations, which represent the relationship between suppliers and offices.
You can create, update, delete, and search for supplier offices with advanced filtering and pagination.
- Version
- 2.0.0
- OpenAPI version
- 3.0.0
Operations
Sezione intitolata “Operations” POST /v2/supplier-office/index
Returns a paginated and filterable list of supplier offices.
Use POST to allow complex filters via JSON payload.
Request Body
Sezione intitolata “Request Body ”Parameters for searching supplier offices
object
object
The unique identifier for the supplier-office relationship.
The unique identifier for the office.
The unique identifier for the supplier.
The code of the supplier.
The name of the supplier.
The street address of the supplier.
The postal code of the supplier.
The region where the supplier is located.
The locality of the supplier.
The country where the supplier is located.
The tax code of the supplier.
The VAT number of the supplier.
The unique identifier for the project.
The name of the project.
The type of the project.
The code of the office.
The name of the office.
Indicates whether the office is owned and active.
Indicates whether the parent office is active.
The field of the model to sort the list for, use a minus to revert the sort. Es -name is to require the sort in reverse order
The field establishes whether to also include historized elements that are no longer active in the results. If you leave this parameter empty the response returns only actual entries.
Example
{ "filter": { "office_id": "off-1", "supplier_id": "sup-1" }, "per-page": 10, "page": 1, "sort": "office_id"}
Responses
Sezione intitolata “ Responses ”List of supplier offices
object
The unique identifier for the supplier-office relationship.
The unique identifier for the office.
The unique identifier for the supplier.
The code of the supplier.
The name of the supplier.
The street address of the supplier.
The postal code of the supplier.
The region where the supplier is located.
The locality of the supplier.
The country where the supplier is located.
The tax code of the supplier.
The VAT number of the supplier.
The unique identifier for the project.
The name of the project.
The type of the project.
The code of the office.
The name of the office.
Indicates whether the office is owned and active.
Indicates whether the parent office is active.
Example
{ "supplier_office_id": "so-1", "office_id": "off-1", "supplier_id": "sup-1", "supplier_name": "Supplier 1", "office_name": "Main Office"}
Headers
Sezione intitolata “Headers ”Current page
Total number of pages
Number of items per page
Total number of items
POST /v2/supplier-office/create
Create a new supplier office by providing the required details.
Request Body required
Sezione intitolata “Request Body required ”Supplier office object to be created
object
The unique identifier for the supplier-office relationship.
The unique identifier for the supplier.
The unique identifier for the office.
Example
{ "office_id": "off-2", "supplier_id": "sup-2"}
Responses
Sezione intitolata “ Responses ”Supplier office created successfully
object
The unique identifier for the supplier-office relationship.
The unique identifier for the supplier.
The unique identifier for the office.
Example
{ "supplier_office_id": "so-2", "office_id": "off-2", "supplier_id": "sup-2"}
GET /v2/supplier-office/view/{id}
Retrieve a supplier office by its unique ID.
Path Parameters
Sezione intitolata “Path Parameters ”ID of the supplier office to retrieve
Responses
Sezione intitolata “ Responses ”Supplier office found
object
The unique identifier for the supplier-office relationship.
The unique identifier for the office.
The unique identifier for the supplier.
The code of the supplier.
The name of the supplier.
The street address of the supplier.
The postal code of the supplier.
The region where the supplier is located.
The locality of the supplier.
The country where the supplier is located.
The tax code of the supplier.
The VAT number of the supplier.
The unique identifier for the project.
The name of the project.
The type of the project.
The code of the office.
The name of the office.
Indicates whether the office is owned and active.
Indicates whether the parent office is active.
Example
{ "supplier_office_id": "so-1", "office_id": "off-1", "supplier_id": "sup-1", "supplier_name": "Supplier 1", "office_name": "Main Office"}
Supplier office not found
DELETE /v2/supplier-office/delete/{id}
Delete a supplier office by its unique ID.
If force=true, all related entities will also be deleted.
Path Parameters
Sezione intitolata “Path Parameters ”ID of the supplier office to delete
Query Parameters
Sezione intitolata “Query Parameters ”Force the deletion of the entity and all related entities
Responses
Sezione intitolata “ Responses ”Supplier office deleted successfully
If force=false, the operation is interrupted and the list of connected entities that will be deleted in case of confirmation (force=true) is returned
PUT /v2/supplier-office/update/{id}
Update an existing supplier office by its unique ID.
Path Parameters
Sezione intitolata “Path Parameters ”ID of the supplier office to update
Request Body required
Sezione intitolata “Request Body required ”Supplier office object with updated data
object
The unique identifier for the supplier-office relationship.
The unique identifier for the supplier.
The unique identifier for the office.
Example
{ "office_id": "off-1"}
Responses
Sezione intitolata “ Responses ”Supplier office updated successfully
object
The unique identifier for the supplier-office relationship.
The unique identifier for the supplier.
The unique identifier for the office.
Example
{ "supplier_office_id": "so-1", "office_id": "off-1"}
Supplier office not found