HTTP Endpoint

Configure URL, method, auth, body type, and tracking location for HTTP flows.

Produce and Consume

Use HTTP as source producer or destination consumer based on run mode. Produce and consume endpoint contracts both require an absolute URL.

Auth

Basic, Bearer, OAuth2 client credentials, and custom headers are supported. For Basic auth, username is required and password may be empty (null is rejected).

Advanced HTTP Fields

Use RequestTimeout to control request duration, TrackingPayloadSource to decide whether tracking extraction reads request or response payload, and ConsumeJsonArrayResponse when destination responses are JSON arrays of messages. RequestTimeout must be positive when explicitly configured.

OAuth2 Client Credentials Fields

OAuth2ClientCredentials supports TokenEndpoint, ClientId, ClientSecret, Scopes, and AdditionalFormFields for token endpoint-specific requirements.

Feature Usage Samples

How to use snippets for HTTP Endpoint.

Switch between C#, Java, Python, TypeScript, and JavaScript to see the native SDK shape for this sample.

Licensing note: every runnable sample requires a valid runner key via WithRunnerKey("...") or config key LoadStrike:RunnerKey.

HTTP Endpoint

var endpoint = new HttpEndpointDefinition
{
    Name = "http-in",
    Mode = TrafficEndpointMode.Produce,
    TrackingField = TrackingFieldSelector.Parse("json:$.trackingId"),
    Url = "https://api.example.com/orders",
    Method = "POST",
    BodyType = HttpRequestBodyType.Json,
    RequestTimeout = TimeSpan.FromSeconds(15),
    MessagePayload = new { trackingId = "trk-1" }
};

Body Example

trackingId

Sample body field that the tracking selector can read when the ID is carried in JSON instead of a header.

RequestTimeout

Optional HTTP timeout override; when set explicitly it must be a positive duration.

{ "trackingId": "trk-1" }

Diagram

HTTP source to destination correlation diagram
HTTP tracking can be extracted from headers or body selectors and correlated downstream.