> 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/invoke-psuendpoint.md). # Invoke-PSUEndpoint Invoke-PSUEndpoint esegue un endpoint API di PowerShell Universal internamente, senza instradare la richiesta attraverso il server web. ## SYNOPSIS Richiama un endpoint API personalizzato internamente. ## SINTASSI ``` Invoke-PSUEndpoint -Url [-Headers ] [-Cookies ] [-Body ] [-Method ] [-ContentType ] [-ResponseVariable ] [-ComputerName ] [-AppToken ] [-Credential ] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [] ``` ## DESCRIZIONE Questo cmdlet offre la possibilità di eseguire un endpoint senza accedere direttamente al server web. ## ESEMPI ### Esempio 1 ```powershell PS C:\> Invoke-PSUEndpoint -URL '/myapi' ``` Restituisce un endpoint API internamente. ## PARAMETRI ### -AppToken Un token dell'app utilizzato per accedere all'endpoint. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Body Il corpo della richiesta HTTP. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -ComputerName Il nome o l'URL del server PowerShell Universal a cui accedere. ```yaml Type: String Parameter Sets: (All) Aliases: Uri Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -ContentType Il valore dell'intestazione HTTP content type. Il valore predefinito è application/json. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Cookies Una hashtable di cookie da inviare all'API. ```yaml Type: Hashtable Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Credential Credenziali per accedere alla Management API di PowerShell Universal. ```yaml Type: PSCredential Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Headers Una hashtable di intestazioni da inviare all'endpoint API. ```yaml Type: Hashtable Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Integrated Se utilizzare il modello di sicurezza integrato. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Method Il metodo HTTP dell'endpoint API. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -TrustCertificate Se il cmdlet deve ignorare i problemi relativi ai certificati. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Url L'URL relativo dell'endpoint API. ```yaml Type: String Parameter Sets: (All) Aliases: Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -UseDefaultCredentials Se utilizzare le credenziali predefinite durante la connessione a PowerShell Universal. Richiede che l'autenticazione di Windows sia abilitata. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -ResponseVariable Specifica il nome della variabile che riceve l'oggetto risposta completo dell'API dopo che l'endpoint è stato richiamato. Il corpo della risposta viene comunque scritto nella pipeline. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False 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, consulti [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). ## INPUT ### Nessuno ## OUTPUT ### System.Object ## NOTE ## COLLEGAMENTI CORRELATI --- # 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/invoke-psuendpoint.md?ask=&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.