> 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/es/comandos-de-powershell/new-udendpoint.md).

# New-UDEndpoint

New-UDEndpoint define un endpoint de API o de script programado de PowerShell Universal que ejecuta código en el servidor y puede requerir roles específicos.

## SINOPSIS

Crea un endpoint programado con un panel.

## SINTAXIS

### Generic (predeterminado)

```
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>]
```

## DESCRIPCIÓN

Crea un endpoint programado con un panel.

## EJEMPLOS

### Ejemplo 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
}
```

Endpoints programados|Almacena en caché un valor aleatorio cada diez segundos

## PARÁMETROS

### -ArgumentList

No obligatorio.

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

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

### -Endpoint

El endpoint que se ejecutará según la programación.

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

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

### -Id

El ID del endpoint.

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

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

### -Role

No se utiliza.

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

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

### -Schedule

La programación que se ejecutará para el endpoint. Utilice New-UDEndpointSchedule para crear un objeto de programación.

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

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

### -JavaScript

El código JavaScript que se ejecutará en el endpoint.

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

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

### CommonParameters

Este cmdlet admite los parámetros comunes: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable y -ProgressAction. Para más información, consulte [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## ENTRADAS

### Ninguna

## SALIDAS

### System.Object

## NOTAS

## ENLACES RELACIONADOS


---

# 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/es/comandos-de-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.