Invoke an inbound HTTP endpoint function.
using System.Net.Http.Headers;var client = new HttpClient();var request = new HttpRequestMessage{ Method = HttpMethod.Patch, RequestUri = new Uri("https://example.com/api/workspace/inbound/example/example"), Content = new StringContent("\"example\"") { Headers = { ContentType = new MediaTypeHeaderValue("application/json") } }};using (var response = await client.SendAsync(request)){ response.EnsureSuccessStatusCode(); var body = await response.Content.ReadAsStringAsync(); Console.WriteLine(body);}const url = 'https://example.com/api/workspace/inbound/example/example';const options = { method: 'PATCH', headers: {'Content-Type': 'application/json'}, body: '"example"'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PATCH \ --url https://example.com/api/workspace/inbound/example/example \ --header 'Content-Type: application/json' \ --data '"example"'Invokes the enabled HTTP endpoint identified by endpointKey. The endpoint configuration selects allowed methods, path, body mode and limits. Authentication is enforced by that configuration: WorkspaceBearer (workspace token or service API key), explicitly enabled Anonymous, SharedSecretHeader or HmacSignature. Absence of a static security requirement here does not grant anonymous access. Header names and HMAC signing rules come from the configured endpoint contract. The function owns request fields, response status, headers and media type; this transport does not use an ApiResponse envelope. Multipart bodies are unsupported. Resolve the concrete endpoint contract before generating a typed business client.
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Request Body
Section titled “Request Body”Endpoint-specific payload: JSON, raw bytes or URL-encoded form according to its configured body mode and size limit.
Examplegenerated
exampleobject
Examplegenerated
Responses
Section titled “Responses”default
Section titled “default”Endpoint-defined status and raw body, or a dispatcher rejection. Unknown/disabled endpoints, authentication, method and intake failures return their HTTP error status with plain text.