The email resource is a thin read surface. AlgaPSA sends and receives mail through its own configured providers and workflows; over the REST API there is one endpoint, GET /email, for reading the tenant's email state.
GET /email is the only operation here. Treat it as a status read rather than a way to send messages — there is no create or send endpoint on this resource. If you need to drive inbound mail into AlgaPSA, model it as an inbound webhook instead.
Every endpoint links through to its full parameters, request and response schemas, and code samples.
GET/api/v1/emailAlgaPSAAlgaDeskGET v1