> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/it/comandi-powershell/new-udendpoint.md).

# New-UDEndpoint

New-UDEndpoint definisce un endpoint API o di script pianificato di PowerShell Universal che esegue codice lato server e può richiedere ruoli specifici.

## SYNOPSIS

Crea un endpoint pianificato con una dashboard.

## SYNTAX

### Generic (Predefinito)

```
New-UDEndpoint [-ArgumentList <Object[]>] [-Id <String>] [-Role <String[]>]
 [<CommonParameters>]
```

### Endpoint

```
New-UDEndpoint -Endpoint <ScriptBlock> [-ArgumentList <Object[]>] [-Id <String>] [-Role <String[]>]
 [<CommonParameters>]
```

### Scheduled

```
New-UDEndpoint -Endpoint <ScriptBlock> [-ArgumentList <Object[]>] [-Id <String>] -Schedule <EndpointSchedule>
 [-Role <String[]>] [<CommonParameters>]
```

### JavaScript

```
New-UDEndpoint -JavaScript <String> [-ArgumentList <Object[]>] [-Id <String>] [-Role <String[]>]
 [<CommonParameters>]
```

## DESCRIPTION

Crea un endpoint pianificato con una dashboard.

## EXAMPLES

### Esempio 1

```powershell
$Schedule = New-UDEndpointSchedule 10 -Second
New-UDEndpoint -Schedule $Schedule -Endpoint {
    $Cache:Random = Get-Random
}
New-UDButton -Text "Get Random" -OnClick {
    Show-UDToast $Cache:Random
}
```

Endpoint pianificati|Memorizza nella cache un valore casuale ogni dieci secondi

## PARAMETERS

### -ArgumentList

Non richiesto.

```yaml
Type: Object[]
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Endpoint

L'endpoint da eseguire in base alla pianificazione.

```yaml
Type: ScriptBlock
Parameter Sets: Endpoint, Scheduled
Aliases:

Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Id

L'ID dell'endpoint.

```yaml
Type: String
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Role

Non utilizzato.

```yaml
Type: String[]
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Schedule

La pianificazione da eseguire per l'endpoint. Utilizzi New-UDEndpointSchedule per creare un oggetto di pianificazione.

```yaml
Type: EndpointSchedule
Parameter Sets: Scheduled
Aliases:

Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -JavaScript

Il codice JavaScript da eseguire sull'endpoint.

```yaml
Type: String
Parameter Sets: JavaScript
Aliases:

Required: True
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters

Questo cmdlet supporta i parametri comuni: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable e -ProgressAction. Per maggiori informazioni, veda [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

### Nessuno

## OUTPUTS

### System.Object

## NOTES

## RELATED LINKS


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/powershell-universal/it/comandi-powershell/new-udendpoint.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.