A service is something billable you sell — managed support, a monitoring tier, an hour of remote work. Services are the catalog you draw from when you build contract lines and invoices. This API is plain CRUD over that catalog.
Every service needs a name, a service type (custom_service_type_id), a billing_method of fixed, hourly, or usage, a default_rate, and a unit_of_measure. The billing method decides how the rate is applied: a flat charge, per hour logged, or per metered unit.
curl https://algapsa.com/api/v1/services \
-H "X-API-Key: $ALGA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"service_name": "Managed Workstation",
"custom_service_type_id": "st_managed",
"billing_method": "fixed",
"default_rate": 4500,
"unit_of_measure": "device"
}'Read one with GET /services/{id}, change its rate or name with PUT /services/{id}, and retire it with DELETE /services/{id}. Editing a service changes the catalog entry; it does not retroactively rewrite contract lines already built from it.
Every endpoint links through to its full parameters, request and response schemas, and code samples.
GET/api/v1/servicesAlgaPSAList servicesPOST/api/v1/servicesAlgaPSACreate serviceGET/api/v1/services/{id}AlgaPSAGet servicePUT/api/v1/services/{id}AlgaPSAUpdate serviceDELETE/api/v1/services/{id}AlgaPSADelete service