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
Cobros → Get
AI-generatedSummary
Retrieve payment (Cobros) records from the Centum ERP system, filtered by optional parameters such as payment ID, customer ID, and document dates, with support for pagination and customizable output formatting.
Inputs
- paymentId — Numeric ID of the payment to retrieve; if specified, fetches a single payment by this ID.
- customerId — Customer identifier to filter payments associated with a specific customer.
- startDate — Start date (FechaDocumentoDesde) to filter payments by document date starting from this date.
- endDate — End date (FechaDocumentoHasta) to filter payments by document date up to this date.
- documentDate (required) — Specific document date (FechaDocumento) used as a parameter in the request, required for operation execution.
- paymentsOutputFormat — Selects output format of the payments data: either wrapped under a single item containing metadata or as individual items per payment.
- simplifiedOutput — Boolean flag indicating whether to return only the most useful top-level fields, reducing output verbosity.
- httpSettings.pagination — Controls pagination mode, either "custom" for configurable per-page fetching or "all" to retrieve all data internally paginated.
- httpSettings.itemsPerPage — Number of items to request per page when using custom pagination.
- httpSettings.pageInterval — Time interval in milliseconds between paginated requests when using custom pagination.
- httpSettings.pageNumber — Starting page number for pagination, defaults to 1.
- debugSettings.enableDebugLogging — Enables logging of sanitized request metadata for debugging purposes.
- debugSettings.debugEndpointContains — Optional filter string to restrict debug logging to requests whose URL contains this substring.
- debugSettings.includeRequestBody — Includes the JSON request body in debug logs if enabled.
Output shape
a JSON object containing either a single item wrapping an array of payment records along with metadata fields (CantidadTotalItems, Pagina) or an array of payment items depending on the 'Output Format' selection
Supports pagination with parameters to control page size and starting page. The 'simplifiedOutput' flag reduces returned fields to the most relevant. Debugging options enable request logging. Date filters and customer/payment identifiers refine result scope.
Examples
Example 1: Fetch all payments for a specific customer within a date range, returning each payment as a separate item
Set 'customerId', 'startDate', and 'endDate'. Use 'paymentsOutputFormat' as 'items'. Configure 'httpSettings' with pagination mode and items per page as needed.
Example 2: Retrieve a specific payment by its ID with full response wrapper and simplified fields
Set 'paymentId' to target the payment. Choose 'paymentsOutputFormat' as 'fullResponse' and enable 'simplifiedOutput' to true.