> 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/da/powershell-kommandoer/invoke-psuendpoint.md). # Invoke-PSUEndpoint Invoke-PSUEndpoint udfører et API-slutpunkt i PowerShell Universal internt, uden at dirigere anmodningen gennem webserveren. ## Synopsis Kalder et brugerdefineret API-slutpunkt internt. ## Syntaks ``` Invoke-PSUEndpoint -Url [-Headers ] [-Cookies ] [-Body ] [-Method ] [-ContentType ] [-ResponseVariable ] [-ComputerName ] [-AppToken ] [-Credential ] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [] ``` ## Beskrivelse Denne cmdlet giver mulighed for at udføre et slutpunkt uden at tilgå webserveren direkte. ## Eksempler ### Eksempel 1 ```powershell PS C:\> Invoke-PSUEndpoint -URL '/myapi' ``` Returnerer et API-slutpunkt internt. ## Parametre ### -AppToken Et app-token, der bruges til at få adgang til slutpunktet. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Body Brødteksten i HTTP-anmodningen. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -ComputerName Navnet eller URL'en på den PowerShell Universal-server, der skal tilgås. ```yaml Type: String Parameter Sets: (All) Aliases: Uri Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -ContentType Værdien af HTTP-indholdstypeheaderen. Standardværdien er 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 En hashtable med cookies, der skal sendes til API'en. ```yaml Type: Hashtable Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Credential Legitimationsoplysninger til at logge på PowerShell Universal Management API. ```yaml Type: PSCredential Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Headers En hashtable med headere, der skal sendes til API-slutpunktet. ```yaml Type: Hashtable Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Integrated Om den integrerede sikkerhedsmodel skal bruges. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Method HTTP-metoden for API-slutpunktet. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -TrustCertificate Om cmdlet'en skal ignorere certifikatproblemer. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -Url Den relative URL til API-slutpunktet. ```yaml Type: String Parameter Sets: (All) Aliases: Required: True Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -UseDefaultCredentials Om standardlegitimationsoplysninger skal bruges ved forbindelse til PowerShell Universal. Kræver, at Windows-godkendelse er aktiveret. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### -ResponseVariable Angiver navnet på den variabel, der modtager det fulde API-svarobjekt, efter at slutpunktet er kaldt. Svarets brødtekst skrives stadig til pipelinen. ```yaml Type: String Parameter Sets: (All) Aliases: Required: False Position: Named Default value: None Accept pipeline input: False Accept wildcard characters: False ``` ### CommonParameters Denne cmdlet understøtter de fælles parametre: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable og -ProgressAction. Se [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216) for at få flere oplysninger. ## Input ### Ingen ## Output ### System.Object ## Noter ## Relaterede links ## Tilladelser Adgangstokenet kræver `apis/execute` for at køre denne cmdlet eksternt. Mål-API-slutpunktet kan også kræve sin egen godkendelse og autorisation. --- # 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/da/powershell-kommandoer/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.