--- title: "Services" slug: "services" description: "A detailed reference for the available services, what each one is responsible for, and how they communicate with the rest of the system." updated: 2026-10-28T13:12:06Z published: 2026-10-28T13:12:06Z canonical: "help.mail-and-deploy.com/services" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.mail-and-deploy.com/llms.txt > Use this file to discover all available pages before exploring further. # Services ### General The [Server](/release36/docs/server) hosts numerous services. These services can be divided in two types: | Service Type | Description | | --- | --- | | User Interface Service | This type of service provides a user interface to which Users can connect using their web browser to edit data in Mail & Deploy. | | Programmatic Service | This type of service does not provide a user interface and you can only connect to it using a programming or scripting language. | ### Service URLs Every service can be reached using a URL that is specific for that service. The general format of that URL will be: Url Components protocol://hostname:port/urlfolder The individual components mean: | Component | Description | | --- | --- | | protocol | Use *http* if you connect to Mail & Deploy using HTTP, otherwise *https* to securely connect to Mail & Deploy. Which protocols may be used depends on the [Server Settings](/release36/docs/server-settings). | | hostname | The host name or IP address of the computer that runs the [Server](/release36/docs/server). | | port | The port on which the Server runs; the [port](/release36/docs/server) can be configured in the [Server Settings](/release36/docs/server-settings) and can be ommitted in the URL if it's the default port for the associated protocol (e.g. if your server runs on port 80 and you use protocol HTTP, you don't have to specify the protocol). | | urlfolder | The URL folder that identifies the service you want to connect to and which [Authentication](/release36/docs/authentication) method you want to use. | **Example:** Suppose you have installed Mail & Deploy on a computer named MDEPLOY and the [Server](/release36/docs/server) runs on port 14999 and has HTTPS enabled. The management service (see below) has been configured in the Server Settings to run with URL folder *Management* for windows authentication and *Management/Custom* for custom authentication. If you want to connect to that service with custom authentication, the correct URL would be: *https://MDEPLOY:14999/Management/Custom*. Which services are available and what protocols, ports, and [Authentication](/release36/docs/authentication) methods are available for each service can be configured in the [Server Settings](/release36/docs/server-settings). ### Services This chapter describes all services available in Mail & Deploy. #### Management Service The management service is a user interface service to which [Users](/release36/docs/users) can connect to in order to perform administrative tasks (such as managing [Users](/release36/docs/users)) and to manage content (such as designing a [Report](/release36/docs/introduction-to-reports) or setting up a [Task](/release36/docs/tasks)). Users connecting to the management service need to fulfill at least one of the following requirements: - They must be of type *Administrator*. - They must have an [Authorization](/release36/docs/authentication) with a *Manage Content* permission in at least one [Workspace](/release36/docs/workspaces). The following [Authentication](/release36/docs/authentication) methods are available for the management service: - Windows Authentication - Custom Authentication - Azure AD Authentication #### Hub Service The hub service is a user interface service that allows [Users](/release36/docs/users) to connect to the Hub which is a self-service portal where users can request the creation of report documents or the execution of Tasks. Users connecting to the hub service need to fulfill at least one of the following requirements: - They must be of type *Administrator*. - They must have an [Authorization](/release36/docs/authentication) with a *Request Reports* or *Execute Task* permission for at least one [Workspace](/release36/docs/workspaces). - They must have an [Authorization](/release36/docs/authentication) with a *Request permission* for at least one [Report](/release36/docs/introduction-to-reports). - They must have an [Authorization](/release36/docs/authentication) with a *Execute permission* for at least one [Task](/release36/docs/tasks). The following [Authentication](/release36/docs/authentication) methods are available for the hub service: - Windows Authentication - Custom Authentication - Azure AD Authentication #### API Service The API service is a service that does not provide a user interface but instead provides a programmatic interface for 3rd party developers to connect to Mail & Deploy through the [API](/release36/docs/introduction-to-mail-and-deploy-api). Users connecting to the API service need to fulfill at least one of the following requirements: - They must be of type *Administrator*. - They must be of type *API User*. The following [Authentication](/release36/docs/authentication) methods are available for the API service: - Custom Authentication - Access Key Authentication #### Heartbeat Service The Heartbeat Service is a service that pings the Mail & Server. It gets the HTTP response 200 if the service is up and running, it will also return the number of Executions currently running. ![Image](https://cdn.document360.io/e3657e0f-d0b6-4032-8271-1f5869a7b807/Images/Documentation/image(66).png) #### Download Service The Download Service is a service that will download a previously created Report that was saved in Download Cache using the [Save Content To Download Cache](/release36/docs/save-content-to-download-cache) Action. http(s)://server:port/download_service_name?token=Document _ID_specified_in_the_Action This Service was introduced in version 3.6.5.