MinimalLambda.Envelopes.ApiGateway
2.3.1
dotnet add package MinimalLambda.Envelopes.ApiGateway --version 2.3.1
NuGet\Install-Package MinimalLambda.Envelopes.ApiGateway -Version 2.3.1
<PackageReference Include="MinimalLambda.Envelopes.ApiGateway" Version="2.3.1" />
<PackageVersion Include="MinimalLambda.Envelopes.ApiGateway" Version="2.3.1" />
<PackageReference Include="MinimalLambda.Envelopes.ApiGateway" />
paket add MinimalLambda.Envelopes.ApiGateway --version 2.3.1
#r "nuget: MinimalLambda.Envelopes.ApiGateway, 2.3.1"
#:package MinimalLambda.Envelopes.ApiGateway@2.3.1
#addin nuget:?package=MinimalLambda.Envelopes.ApiGateway&version=2.3.1
#tool nuget:?package=MinimalLambda.Envelopes.ApiGateway&version=2.3.1
MinimalLambda.Envelopes.ApiGateway
Strongly-typed API Gateway event handling for the MinimalLambda framework.
Overview
This package provides strongly-typed envelopes for handling API Gateway events in Lambda functions. It contains classes that can be used as input and output types for Lambda functions that process REST APIs, HTTP APIs (payload format 1.0), WebSocket APIs, HTTP APIs (payload format 2.0), and Lambda Function URLs.
The envelopes extend the base
APIGatewayProxyRequest,
APIGatewayProxyResponse,
and HTTP API equivalents with strongly-typed BodyContent properties for easier request/response
serialization:
| Envelope Class | Base Class | Use Case |
|---|---|---|
ApiGatewayRequestEnvelope<T> |
APIGatewayProxyRequest |
REST API, HTTP API payload format 1.0, or WebSocket API requests with deserialized body |
ApiGatewayResponseEnvelope<T> |
APIGatewayProxyResponse |
REST API, HTTP API payload format 1.0, or WebSocket API responses with typed body |
ApiGatewayV2RequestEnvelope<T> |
APIGatewayHttpApiV2ProxyRequest |
HTTP API payload format 2.0 requests with deserialized body |
ApiGatewayV2ResponseEnvelope<T> |
APIGatewayHttpApiV2ProxyResponse |
HTTP API payload format 2.0 responses with typed body |
ApiGatewayResult |
APIGatewayProxyResponse |
REST/HTTP/WebSocket API responses with fluent API |
ApiGatewayV2Result |
APIGatewayHttpApiV2ProxyResponse |
HTTP API v2 responses with fluent API |
Quick Start
Define your request and response types, then create a handler:
using System;
using System.Collections.Generic;
using MinimalLambda.Builder;
using MinimalLambda.Envelopes.ApiGateway;
using Microsoft.Extensions.Hosting;
using Microsoft.Extensions.Logging;
var builder = LambdaApplication.CreateBuilder();
var lambda = builder.Build();
// ApiGatewayRequestEnvelope<Request> provides the API Gateway event with deserialized request body
// ApiGatewayResponseEnvelope<Response> wraps the response and serializes it to the body
lambda.MapHandler(
([FromEvent] ApiGatewayRequestEnvelope<Request> request, ILogger<Program> logger) =>
{
logger.LogInformation("Request: {Name}", request.BodyContent?.Name);
return new ApiGatewayResponseEnvelope<Response>
{
BodyContent = new Response($"Hello {request.BodyContent?.Name}!", DateTime.UtcNow),
StatusCode = 200,
Headers = new Dictionary<string, string> { ["Content-Type"] = "application/json" },
};
}
);
await lambda.RunAsync();
// Your request and response payloads
internal record Request(string Name);
internal record Response(string Message, DateTime TimestampUtc);
For HTTP API v2, use ApiGatewayV2RequestEnvelope<T> and ApiGatewayV2ResponseEnvelope<T> in the
same way.
Response Builder API
The ApiGatewayResult and ApiGatewayV2Result classes provide fluent APIs for building HTTP
responses. Key benefit: Return multiple strongly typed models from the same handler (e.g.,
success vs. error responses with different types).
// REST API / HTTP API v1 / WebSocket
lambda.MapHandler(([FromEvent] ApiGatewayRequestEnvelope<Request> request) =>
{
if (string.IsNullOrEmpty(request.BodyContent?.Name))
return ApiGatewayResult.BadRequest(new ErrorResponse("Name is required"));
return ApiGatewayResult.Ok(new SuccessResponse($"Hello {request.BodyContent.Name}!"));
});
// HTTP API v2
lambda.MapHandler(([FromEvent] ApiGatewayV2RequestEnvelope<Request> request) =>
{
if (string.IsNullOrEmpty(request.BodyContent?.Name))
return ApiGatewayV2Result.BadRequest(new ErrorResponse("Name is required"));
return ApiGatewayV2Result.Ok(new SuccessResponse($"Hello {request.BodyContent.Name}!"));
});
Available methods: Ok(), Created(), NoContent(), BadRequest(), Unauthorized(),
NotFound(), Conflict(), UnprocessableEntity(), InternalServerError(), StatusCode(int),
Text(int, string), Json<T>(int, T).
All methods have overloads with and without body content. Use .Customize() for fluent header
customization.
Both result classes use their respective envelope classes internally.
Choosing Between Envelopes and Results
Use ApiGatewayResult / ApiGatewayV2Result when you need to return multiple strongly typed
models from the same handler (e.g., different success and error types). Provides convenient methods
for common HTTP status codes.
Use envelope classes directly when you need custom serialization (e.g., XML) or want to extend envelope base classes for custom behavior.
Custom Envelopes
To implement custom deserialization logic, extend the appropriate base class and override the payload handling method:
// Example: Custom XML deserialization for requests
public sealed class XmlApiGatewayXmlRequestEnvelope<T> : ApiGatewayRequestEnvelopeBase<T>
{
public override void ExtractPayload(EnvelopeOptions options)
{
using var stringReader = new StringReader(Body);
using var xmlReader = XmlReader.Create(stringReader, options.XmlReaderSettings);
var serializer = new XmlSerializer(typeof(T));
BodyContent = (T)serializer.Deserialize(xmlReader)!;
}
}
// Example: Custom XML serialization for responses
public sealed class XmlApiGatewayXmlResponseEnvelope<T> : ApiGatewayResponseEnvelopeBase<T>
{
public override void PackPayload(EnvelopeOptions options)
{
using var stringWriter = new StringWriter();
using var xmlWriter = XmlWriter.Create(stringWriter, options.XmlWriterSettings);
var serializer = new XmlSerializer(typeof(T));
serializer.Serialize(xmlWriter, BodyContent);
Body = stringWriter.ToString();
}
}
This pattern allows you to support multiple serialization formats while maintaining the same envelope interface.
AOT Support
When using .NET Native AOT, register all envelope and payload types in your JsonSerializerContext:
[JsonSerializable(typeof(ApiGatewayRequestEnvelope<Request>))]
[JsonSerializable(typeof(ApiGatewayResponseEnvelope<Response>))]
[JsonSerializable(typeof(Request))]
[JsonSerializable(typeof(Response))]
internal partial class SerializerContext : JsonSerializerContext;
When using ApiGatewayResult / ApiGatewayV2Result with multiple return types, register each
type separately:
[JsonSerializable(typeof(ApiGatewayRequestEnvelope<Request>))]
[JsonSerializable(typeof(ApiGatewayResult))]
[JsonSerializable(typeof(Request))]
[JsonSerializable(typeof(SuccessResponse))]
[JsonSerializable(typeof(ErrorResponse))]
internal partial class SerializerContext : JsonSerializerContext;
Register the serializer and configure envelope options to use the context:
builder.Services.AddLambdaSerializerWithContext<SerializerContext>();
builder.Services.ConfigureEnvelopeOptions(options =>
{
options.JsonOptions.TypeInfoResolver = SerializerContext.Default;
});
The context must be registered as the type resolver for both the envelope options and the Lambda serializer because the Lambda event and envelope payload are deserialized at different steps: the Lambda serializer deserializes the raw event, and the envelope options deserialize the envelope content into your payload type.
Other Packages
Additional packages in the minimal-lambda framework for abstractions, observability, and event source handling.
License
This project is licensed under the MIT License. See LICENSE for details.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Amazon.Lambda.APIGatewayEvents (>= 2.7.3)
- Amazon.Lambda.Core (>= 2.8.1)
- MinimalLambda.Abstractions (>= 2.3.1)
- MinimalLambda.Envelopes (>= 2.3.1)
-
net8.0
- Amazon.Lambda.APIGatewayEvents (>= 2.7.3)
- Amazon.Lambda.Core (>= 2.8.1)
- MinimalLambda.Abstractions (>= 2.3.1)
- MinimalLambda.Envelopes (>= 2.3.1)
-
net9.0
- Amazon.Lambda.APIGatewayEvents (>= 2.7.3)
- Amazon.Lambda.Core (>= 2.8.1)
- MinimalLambda.Abstractions (>= 2.3.1)
- MinimalLambda.Envelopes (>= 2.3.1)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.3.1 | 90 | 3/23/2026 |
| 2.3.0 | 87 | 3/21/2026 |
| 2.2.0 | 104 | 1/12/2026 |
| 2.2.0-beta.1 | 64 | 1/9/2026 |
| 2.1.1 | 187 | 12/22/2025 |
| 2.1.0-beta.6 | 107 | 12/20/2025 |
| 2.1.0-beta.5 | 142 | 12/19/2025 |
| 2.1.0-beta.4 | 151 | 12/19/2025 |
| 2.1.0-beta.3 | 150 | 12/19/2025 |
| 2.1.0-beta.2 | 152 | 12/19/2025 |
| 2.1.0-beta.1 | 232 | 12/19/2025 |
| 2.0.0 | 282 | 12/18/2025 |
| 2.0.0-beta.11 | 233 | 12/17/2025 |
| 2.0.0-beta.10 | 232 | 12/17/2025 |
| 2.0.0-beta.9 | 227 | 12/15/2025 |
| 2.0.0-beta.8 | 214 | 12/15/2025 |
| 2.0.0-beta.7 | 179 | 12/15/2025 |
| 2.0.0-beta.6 | 178 | 12/14/2025 |
| 2.0.0-beta.5 | 174 | 12/14/2025 |
| 2.0.0-beta.4 | 124 | 12/13/2025 |