Editar

Compartir a través de

Kiota request builders

  • Artículo

The primary goal of a request builder class is to enable a developer to easily construct an HTTP request. By using a set of related request builder classes, we can enable a developer to construct an HTTP request for any resource exposed by an HTTP API.

There are three phases of constructing the HTTP request. Building the URL, specifying query parameters, and selecting the HTTP method.

Building the URL

By creating properties on request builder classes, the developer can effectively construct a URL by navigating the hierarchy of request builders, aided by the editor's autocomplete.

The URL for the request is built using an RFC6570 URL Template and providing its parameters.

var todo = await todoClient.ToDos["<todoId>"].GetAsync();
var responsiblePerson = await todoClient.ToDos["<todoId>"].AssignedTo.GetAsync();

Each request builder class exposes the set of HTTP methods that are supported on that resource. Each operation method allows setting and configuring query parameters, setting HTTP headers, and providing a custom response handler.

Request builders are generated into a subnamespace following the API path they refer to.

Default members

Each request builder contains a default set of members to help build the URL and ultimately the requests.

Path parameters

The path parameters dictionary/map contains a list of the parameters for the URL template. The fluent API builds the URL using those parameters, and the parameters are passed along from request builder to request builder.

Considering the following sample:

var requestBuilder = todoClient.TaskLists["taskListId"].ToDos["todoId"].AssignedTo;

Path parameters for the requestBuilder variable contain two entries:

  • task_list_id of value taskListId.
  • todo_id of value todoId.

When the request adapter executes the request, it resolves all parameters (path and query) against the URL template. The base URL parameter value is also provided at that time.

UrlTemplate

The request builder has a Url Template property. This template is resolved using the path and query parameters to get the definitive URL to use for the request.

Consider the following sample:

var requestBuilder = todoClient.TaskLists["taskListId"].ToDos["todoId"].AssignedTo;

The URL template for the requestBuilder looks something like {+baseurl}/taskLists/{task_list_id}/toDos/{todo_id}/assignedTo{?select,expand}.

Note

The query parameters will only be present if included in the OpenAPI description.

The request adapter provides the path and query parameters, and the base URL before the request is executed.

RequestAdapter

In order to execute any request, the request builder needs to have access to a request adapter.

This request adapter is passed from request builder to request builder when using the fluent style API. This object holds most of the client configuration, serialization, and deserialization capabilities and more.

Constructors

Request builders offer two different constructors (one if the target language supports types unions).

public UsersRequestBuilder(Dictionary<string, object> pathParameters, IRequestAdapter requestAdapter);
public UsersRequestBuilder(string rawUrl, IRequestAdapter requestAdapter)

The first constructor (dictionary) is meant to be used by the fluent API infrastructure to pass in the path parameters from previous request builders.

The second constructor is meant to be used by developers when they need to use the request builder with a raw URL they already have. Multiple scenarios require such use: delta links, paging through collections, resuming from going offline...

Note

Once the raw URL is set for a given request builder, and subsequently for a given request, the path and query parameters on the request information will be reset, and the request adapter will not attempt to resolve the template anymore, it will read the provided raw URL as is.

Besides executing requests and getting the deserialized result, request builders also act as the foundation for the fluent style API.

Properties

Properties are used for navigation path segments that declare no parameters.

In the following example:

var requestBuilder = todoClient.TaskLists["taskListId"].ToDos["todoId"].AssignedTo;

Two navigation properties are in use in this fluent style API call: .TaskLists and .ToDos

The underlying URL template looks like {+baseurl}/taskLists/{task_list_id}/toDos/{todo_id}/assignedTo{?select,expand}, where both the taskLists and toDos path segments don't require any parameter.

Note

If the target language doesn't support auto-property getters (get keyword in C# or TypeScript) a method with no parameter will be used instead.

This property always returns a value (non-null) and never throws an exception.

Indexers

Indexers are used for navigation path segments that declare a single unnamed parameter. This design choice was made as APIs often use that pattern for indexable collections endpoints.

In the following example:

var requestBuilder = todoClient.TaskLists["taskListId"].ToDos["todoId"].AssignedTo;

Two indexers are used where brackets are present.

The underlying URL template looks like {+baseurl}/taskLists/{task_list_id}/toDos/{todo_id}/assignedTo{?select,expand}, where both the {task_list_id} and {todo_id} path segments are single unnamed path parameters.

It's important to note that even if an endpoint to index in the collection {+baseurl}/taskLists/{task_list_id} doesn't exist, it doesn't affect the generation of the fluent style API for the endpoint. If that indexing endpoint does exist, the only effect is to the parent request builder that exposes a Get method.

Note

For languages that do not support indexers, a method with a suffix and a single parameters is used instead.

var requestBuilder = todoClient.taskLists().byTaskListId("taskListId").toDos().byToDoId("todoId").assignedTo;

This indexer always returns a value (non-null) and never throws an exception.

Method with parameters

Methods with parameters are used when path segments contain named parameters or multiple parameters.

In the following example:

var requestBuilder = todoClient.TaskLists["taskListId"].GetReminders("startDate", "endDate");

One method with two parameters is present.

The underlying URL template looks like {+baseurl}/taskLists/{task_list_id}/getReminders(startDate='{startDate}',endDate='{endDate}')/{?select,expand}, when the getReminders path segment contains two named parameters startDate and endDate.

This method with parameters always returns a value (non-null) and never throw an exception.

WithUrl

Request builders offer a WithUrl method to facilitate the interoperability between the fluent API surface and raw URLs coming from other sources.

Let's assume the following call returns a URL to the next page, a common practice for REST APIs.

var page1 = await client.Customers["Jane"].Orders.GetAsync();
page1.NextPageUrl;

You can still use the fluent API and get the benefits of autocompletion, compile-time validation and more by using the WithUrl method.

var page1 = await client.Customers["Jane"].Orders.WithUrl(page1.NextPageUrl).GetAsync();

Note

In this example, any path parameter (any value passed before the WithUrl method) as well as any query parameter (passed to the executor/GetAsync method) will be ignored.

[!INFO] Always use the WithUrl method in the right-most position before the executor method (GetAsync), this way the data types for the request and response bodies will match what you expect.

Request building and execution

Once the request path is built using the fluent style API, request builders provide methods to generate and execute requests.

Request generators

Request generator methods follow this Create{HTTPMethodName}RequestInformation naming convention. And accept the following parameters:

  • body: the request body if supported.
  • query parameters: an object or callback to set the request query parameters.
  • headers: an object or callback to set the request headers.
  • options: a list of request options to set for the request. The middleware pipeline is the primary consumer of these options.

These methods return an abstract request information object that can be passed to the request adapter for execution, or used with other tasks (for example, batching of requests).

Request executors

Request executor methods follow this {HTTPMethodName}{Suffix} naming convention, where a suffix is applied when it makes sense for the target language (for example, GetAsync in C#). These methods accept the same parameter set as the request generators as they call into these methods to generate the request and then pass the request information to the request adapter for execution. They provide an extra parameter:

  • responseHandler: this parameter might be used to bypass the standard response handling for the current request and access the native HTTP response object.