A product is a catalog item you resell — hardware, a license, anything you stock and mark up. Products and services share one underlying schema, so the fields look familiar, but a product always bills by usage and carries a SKU and cost.
The create body reuses the service fields, including service_name for the product name. The differences are what matter: billing_method is fixed to usage, and a product adds sku, cost, cost_currency, and currency_code so you can track margin. Required fields are service_name, custom_service_type_id, and unit_of_measure.
curl https://algapsa.com/api/v1/products \
-H "X-API-Key: $ALGA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"service_name": "USB-C Docking Station",
"custom_service_type_id": "st_hardware",
"unit_of_measure": "unit",
"sku": "DOCK-USBC-01",
"default_rate": 18900,
"cost": 12000,
"cost_currency": "USD"
}'GET /products lists the catalog and GET /products/{id} reads one. Update price or cost with PUT /products/{id}; remove a discontinued item with DELETE /products/{id}.
Every endpoint links through to its full parameters, request and response schemas, and code samples.
GET/api/v1/productsAlgaPSAList productsPOST/api/v1/productsAlgaPSACreate productGET/api/v1/products/{id}AlgaPSAGet productPUT/api/v1/products/{id}AlgaPSAUpdate productDELETE/api/v1/products/{id}AlgaPSADelete product