pub package github last commit github last commit github last commit

A simple yet powerful wrapper around http library which provide:

HTTP Requestsโœ…
HTTP interval requestsโœ…
HTTP Requests from widget treeโœ…
HTTP Middlewares ApiLinkโœ… ๐Ÿงช
App state managementโœ… ๐Ÿงช
State management from widget treeโœ… ๐Ÿงช
Client for graphQLโš™๏ธ
ApiLink for request cachingโŒ

โœ… - done
๐Ÿงช - experimental
โš™๏ธ - work in progress
โŒ - not implemented


This library is under development, breaking API changes might still happen. If you would like to make use of this library please make sure to provide which version you want to use e.g:

  restui: 0.1.0

1. Getting Started

1.1. First create your Api class by extending BaseApi class

class Api extends ApiBase {

    @required Uri uri,
    ApiLink link,
    Map<String, String> defaultHeaders,
    List<ApiStore> stores,
  }) : super(
          uri: uri,
          defaultHeaders: defaultHeaders,
          link: link,
          stores: stores,

  /// Implement methods that will call your api
  Future<ExamplePhotoModel> getRandomPhoto() async {

    /// It's important to triggers http requests with [call] method
    final response = await call(
      endpoint: "/id/${Random().nextInt(50)}/info",
      method: HttpMethod.GET,
    return ExamplePhotoModel.fromJson(json.decode(response.body));

1.2. Provide your Api instance down the widget tree

class MyApp extends StatelessWidget {
  Widget build(BuildContext context) {

    return RestuiProvider<Api>(
        apiBuilder: (_) => Api(
          uri: Uri.parse(""),
          link: HeadersMapperLink(["uid", "client", "access-token"])
              .chain(DebugLink(printResponseBody: true)),
          stores: <ApiStore>[
        child: MaterialApp(
          title: 'flutter_starter_app',
          onGenerateRoute: _generateRoute,

1.3. Make use of Query widget to make the API call from widget tree

For more information look HERE

class _ApiExampleScreenState extends State<ApiExampleScreen> {
  Widget build(BuildContext context) {
    return Query<ExamplePhotoModel, Api, void>(
      callBuilder: (BuildContext context, Api api, void variable) =>
      builder: (BuildContext context, bool loading, ExamplePhotoModel value) {
        return Center(
          /// Implementation ...

2. Query widget

Query widget is the hearth of Restui library. It allows you to handle API calls and app state management from one widget.

For example of state management and api calls look at example app.

class _ApiExampleScreenState extends State<ApiExampleScreen> {
  Widget build(BuildContext context) {
    bool hasPhotot = _randomPhoto != null;

    /// `Query<R, A extends BaseApi, V>`
    /// [R] is type of value that will be returned from [callBuilder] and passed to [builder]
    /// as a [value] argument
    /// [A] is your api class implementation
    /// [V] is a variable type
    return Query<ExamplePhotoModel, Api, MyVariable>(
      /// Specifying [interval] will cause the query to be
      /// called periodically every [interval] of time.
      interval: const Duration(seconds: 10),

      /// Whether [callBuilder] will be called right before first
      /// [builder] invocation defaults to `true`.
      /// If `false` then [callBuilder] can be called by invocation of  [call] method from
      /// [QueryState] which can be retrieved by [GlobalKey] assigned to [key] argument
      instantCall: false,

      /// Variable of type [V]
      /// Will be passed to the [callBuilder] method
      variable _myVariable,

      /// Data returned from [initialDataBuilder] will be passed
      /// as [value] argument to [builder] method when [callBuilder]
      /// does not return the value yet.
      initialDataBuilder: (BuildContext context, Api api) => _initialData,
      /// This argument is REQUIRED
      /// [callBuilder] is the place when you can and should make api request.
      /// It is responsible for getting data and passing it into [builder] function
      /// as [value] argument.
      /// TIP:
      /// If data is inside your [ApiStorage] you can return it instead of making api call.
      callBuilder: (BuildContext context, Api api, MyVariable variable) async =>

      /// [onComplete] is called only when [callBuilder] function returned succesfuly
      /// without throwing an [Exception]. Throwing an [Exception] from [callBuilder]
      /// will cause [onError] function invocation instead.
      /// [onComplete] callback is called after [callBuilder] with
      /// the data returned from it. Called just before [builder] invocation.
      onComplete: (BuildContext context, ExamplePhotoModel photo) {
         /// Implementation ...

      /// If [callBuilder] function will throw an [Exception] it will be
      /// catched and passed to [onError] function if it's provided.
      onError: (Exception exception) {

      /// This works like an [Updater] widget, [AnimationBuilder], [StreamBuilder] etc.
      /// [updaterBuilder] is called right before first widget build. It must return [Listenable]
      /// object. Returning null will take no effect.
      /// [Query] widget will call [builder] every time when [Listenable] returned from
      /// [updaterBuilder] will notify his listeners.
      /// TIP:
      /// You can use [NotifierApiStore] class to create your own [ApiStore]  with [ChangeNotifier].
      /// After that you are able to retrieve this store and update widget by calling [builder]
      /// method every time it will notify listeners.
      updaterBuilder: (BuildContext context, Api api) =>

      /// This method is called before every [builder] invocation triggered by [Listenable]
      /// returned from [updaterBuilder] or [callBuilder] method invocation.
      /// Returning [false] from this method will prevent calling [builder].
      /// Returning null will take no effect.
      shouldUpdate: (BuildContext context, Api api, ExamplePhotoModel value) => true, 

      /// This argument is REQUIRED
      /// [value] will be [null] or [initialData] (if argument provided) untill
      /// first value are returned from [callBuilder].
      /// [loading] indicates whether [callBuilder] method is ongoing.
      builder: (BuildContext context, bool loading, ExamplePhotoModel value) {
        return Center(
          /// Implementation ...

ApiLink object is kind of a middleware that enables you to add some custom behaviour before and after every API request.

Links can be then Retrieved from your API class MORE.

This ApiLink takes headers specified by headersToMap argument from response headers and then put to the next request headers.

It can be used for authorization. For example,we have an authorization header that changes after each request and with the next query we must send it back in headers. This ApiLink will take it from the response, save and set as a next request header.

Example use simple as:

final api = Api(
  uri: Uri.parse(""),
  link: HeadersMapperLink(["authorization"]),

If you want to create your own ApiLink with custom behaviour all you need to do is to create your link class that extend ApiLink class and then pass it to your api super constructor (constructor of ApiBase class) (e.g. [1] [2]).

class OngoingRequestsCounterLink extends ApiLink {
  int ongoingRequests;

  OngoingRequestsCounterLink() : _requests = 0;

  /// All you need to do is to override [next] method and add your
  /// custom behaviour
  Future<ApiResponse> next(ApiRequest request) async {
    /// Code here will be called `BEFORE` request

    /// Calling [] is required. It calls next [ApiLink]s in the 
    /// chain and returns with [ApiResponse]. 
    ApiResponse response = await;

    /// Code here will be called `AFTER` request

    /// [next] method should return [ApiResponse] as it passes it down the
    /// [ApiLink] chain
    return response;

Sometimes there is a need to retrieve data saved inside a link or pass some data into it. This is possible thanks to the:

/// Retrieve `Api` instance from the tree
Api api = Query.of<Api>(context);

/// Get first link of provided type
OngoingRequestsCounterLink link = Api.getFirstLinkOfType<OngoingRequestsCounterLink>();

/// Do sth with your link data

Api should be replaced with your API class name that extends ApiBase.

4. State management (experimental)

Often inside our app state we are keeping modified results of our api requests. Updating an app state based on api result is often a pain. This library simplifies this process.

5. Example app

Inside example directory you can find an example app and play with this library.

5.1 Api example

5.2 Api + state management


6. TODO:

  • Tests
  • GraphQLApiBase class responsible for graphQL requests
  • Improve readme
  • Add CacheLink which will be responsible for request caching