Actions76
- Access Token Actions
- Ajustes Movimientos Stock Actions
- Articulos Actions
- Bonificaciones Actions
- Categorías Articulo Actions
- Choferes Actions
- Choferes Guía Logística Actions
- Clientes Actions
- Cobros Actions
- Compras Actions
- Conceptos Actions
- Condiciones Venta Actions
- Departamentos Actions
- Divisiones Empresa Grupo Economico Actions
- Frecuencia Clientes Actions
- Listas Precios Actions
- Marcas Actions
- Operadores Móviles Actions
- Orden Traspaso Actions
- Órdenes Compra Actions
- Países Actions
- Pedidos Venta Actions
- Promociones Comerciales Actions
- Proveedores Actions
- Provincias Actions
- Regimenes Especiales Actions
- Remitos Compra Actions
- Remitos Venta Actions
- Rubros Actions
- Secciones Sucursales Actions
- SubRubros Actions
- Sucursales Físicas Actions
- Tipos Comprobante Actions
- Transportes Actions
- Turnos Entrega Actions
- Ubicaciones Artículos Actions
- Vendedores Actions
- Ventas Actions
Compras → Create
AI-generatedSummary
Create a new purchase record in the Centum ERP system with specified invoice details, supplier, and article quantities.
Inputs
- articleIds (required) — Comma-separated list of positive integer article IDs to include in the purchase. Spaces are ignored.
- articleQuantities (required) — Comma-separated list of positive integer quantities corresponding to each article ID, matching order.
- purchaseSupplierId (required) — Supplier ID associated with the purchase.
- voucherCode — Code of the purchase voucher (e.g. FCC).
- voucherTypeId — ID of the invoice voucher type.
- voucherTypeName — Name of the invoice voucher type.
- documentLetter — Letter of the purchase invoice document.
- documentNumber — Number of the purchase invoice document.
- pointOfSale — Point-of-sale number for the document.
- startDate — Document date/time for the purchase.
- debugSettings — Advanced debug options for logging request details.
Output shape
a single record representing the newly created purchase, including its data fields as returned by the Centum ERP API.
The output contains the created purchase's details as structured by the ERP response. Debug logging can be optionally enabled to capture request metadata but does not affect output shape.