SYNOPSIS

        use API::Trello;
    
        my $trello = API::Trello->new(
            key        => 'KEY',
            token      => 'TOKEN',
            identifier => 'APPLICATION (yourname@example.com)',
        );
    
        my $board = $trello->boards(1);
        my $results = $board->fetch;
    
        # after some introspection
    
        $board->delete;

DESCRIPTION

    This distribution provides an object-oriented thin-client library for
    interacting with the Trello (http://trello.com) API. For usage and
    documentation information visit
    https://trello.com/docs/gettingstarted/index.html.

THIN CLIENT

    A thin-client library is advantageous as it has complete coverage and
    can easily adapt to changes in the API with minimal effort. As a
    thin-client library, this module does not map specific HTTP requests to
    specific routines nor does it provide parameter validation, pagination,
    or other conventions found in typical API client implementations,
    instead, it simply provides a simple and consistent mechanism for
    dynamically generating HTTP requests. Additionally, this module has
    support for debugging and retrying API calls as well as throwing
    exceptions when 4xx and 5xx server response codes are received.

 Building

        my $board = $trello->boards(1);
        my $checklists = $board->checklists;
    
        $checklists->action; # GET /boards/1/checklists
        $checklists->action('head'); # HEAD /boards/1/checklists

    Building up an HTTP request object is extremely easy, simply call
    method names which correspond to the API's path segments in the
    resource you wish to execute a request against. This module uses
    autoloading and returns a new instance with each method call. The
    following is the equivalent:

        my $board = $trello->resource(boards => 1);
        my $checklists = $board->resource('checklists');
    
        # or
    
        my $checklists = $trello->resource('boards', 1, 'checklists');
    
        # then
    
        $checklists->action('put', %args); # PUT /boards/1/checklists

    Because each call returns a new API instance configured with a resource
    locator based on the supplied parameters, reuse and request isolation
    are made simple, i.e., you will only need to configure the client once
    in your application.

 Fetching

        my $boards = $trello->boards;
    
        $boards->fetch(
            query => {
                # query-string parameters
            },
        );
    
        # equivalent to
    
        $trello->resource('boards')->action(
            get => ( query => { ... } )
        );

    This example illustrates how you might fetch an API resource.

 Creating

        my $boards = $trello->boards;
    
        $boards->create(
            data => {
                # content-body parameters
            },
            query => {
                # query-string parameters
            },
        );
    
        # or
    
        my $boards = $trello->boards->create(...);
    
        # equivalent to
    
        $trello->resource('boards')->action(
            post => ( query => { ... }, data => { ... } )
        );

    This example illustrates how you might create a new API resource.

 Updating

        my $boards = $trello->boards;
        my $board  = $boards->resource(1);
    
        $board->update(
            data => {
                # content-body parameters
            },
            query => {
                # query-string parameters
            },
        );
    
        # or
    
        my $board = $trello->boards(1);
    
        $board->update(...);
    
        # equivalent to
    
        $trello->resource('boards')->action(
            put => ( query => { ... }, data => { ... } )
        );

    This example illustrates how you might update an new API resource.

 Deleting

        my $boards = $trello->boards;
        my $board  = $boards->resource(1);
    
        $board->delete(
            data => {
                # content-body parameters
            },
            query => {
                # query-string parameters
            },
        );
    
        # or
    
        my $board = $trello->boards(1);
    
        $board->delete(...);
    
        # equivalent to
    
        $trello->resource('boards')->action(
            delete => ( query => { ... }, data => { ... } )
        );

    This example illustrates how you might delete an API resource.

 Transacting

        my $board = $trello->resource('boards', '1');
    
        my ($results, $transaction) = $board->fetch(...);

    This example illustrates how you can access the transaction object used
    to submit the HTTP request.

        $trello->key;
        $trello->key('KEY');

    The key parameter should be set to the account holder's API key.

        $trello->token;
        $trello->token('TOKEN');

    The token parameter should be set to the account holder's API access
    token.

        $trello->identifier;
        $trello->identifier('IDENTIFIER');

    The identifier parameter should be set using a string to identify your
    app.

        $trello->debug;
        $trello->debug(1);

    The debug attribute if true prints HTTP requests and responses to
    standard out.

        $trello->fatal;
        $trello->fatal(1);

    The fatal attribute if true promotes 4xx and 5xx server response codes
    to exceptions, a API::Trello::Exception object.

        $trello->retries;
        $trello->retries(10);

    The retries attribute determines how many times an HTTP request should
    be retried if a 4xx or 5xx response is received. This attribute
    defaults to 0.

        $trello->timeout;
        $trello->timeout(5);

    The timeout attribute determines how long an HTTP connection should be
    kept alive. This attribute defaults to 10.

        $trello->url;
        $trello->url(Mojo::URL->new('https://api.trello.com'));

    The url attribute set the base/pre-configured URL object that will be
    used in all HTTP requests. This attribute expects a Mojo::URL object.

        $trello->user_agent;
        $trello->user_agent(Mojo::UserAgent->new);

    The user_agent attribute set the pre-configured UserAgent object that
    will be used in all HTTP requests. This attribute expects a
    Mojo::UserAgent object.

        my $result = $trello->action($verb, %args);
    
        # e.g.
    
        $trello->action('head', %args);   # HEAD request
        $trello->action('optons', %args); # OPTIONS request
        $trello->action('patch', %args);  # PATCH request

    The action method issues a request to the API resource represented by
    the object. The first parameter will be used as the HTTP request
    method. The arguments, expected to be a list of key/value pairs, will
    be included in the request if the key is either data or query.

        my $results = $trello->create(%args);
    
        # or
    
        $trello->POST(%args);

    The create method issues a POST request to the API resource represented
    by the object. The arguments, expected to be a list of key/value pairs,
    will be included in the request if the key is either data or query.

        my $results = $trello->delete(%args);
    
        # or
    
        $trello->DELETE(%args);

    The delete method issues a DELETE request to the API resource
    represented by the object. The arguments, expected to be a list of
    key/value pairs, will be included in the request if the key is either
    data or query.

        my $results = $trello->fetch(%args);
    
        # or
    
        $trello->GET(%args);

    The fetch method issues a GET request to the API resource represented
    by the object. The arguments, expected to be a list of key/value pairs,
    will be included in the request if the key is either data or query.

        my $results = $trello->update(%args);
    
        # or
    
        $trello->PUT(%args);

    The update method issues a PUT request to the API resource represented
    by the object. The arguments, expected to be a list of key/value pairs,
    will be included in the request if the key is either data or query.

        $trello->actions;

    The actions method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/action/index.html.

        $trello->batch;

    The batch method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/batch/index.html.

        $trello->boards;

    The boards method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/board/index.html.

        $trello->cards;

    The cards method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/card/index.html.

        $trello->checklists;

    The checklists method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/checklist/index.html.

        $trello->labels;

    The labels method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/label/index.html.

        $trello->lists;

    The lists method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/list/index.html.

        $trello->members;

    The members method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/member/index.html.

        $trello->notifications;

    The notifications method returns a new instance representative of the
    API resource requested. This method accepts a list of path segments
    which will be used in the HTTP request. The following documentation can
    be used to find more information.
    https://trello.com/docs/api/notification/index.html.

        $trello->organizations;

    The organizations method returns a new instance representative of the
    API resource requested. This method accepts a list of path segments
    which will be used in the HTTP request. The following documentation can
    be used to find more information.
    https://trello.com/docs/api/organization/index.html.

        $trello->search;

    The search method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/search/index.html.

        $trello->sessions;

    The sessions method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/session/index.html.

        $trello->tokens;

    The tokens method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/token/index.html.

        $trello->types;

    The types method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/type/index.html.

        $trello->webhooks;

    The webhooks method returns a new instance representative of the API
    resource requested. This method accepts a list of path segments which
    will be used in the HTTP request. The following documentation can be
    used to find more information.
    https://trello.com/docs/api/webhook/index.html.

POD ERRORS

    Hey! The above document had some coding errors, which are explained
    below:

    Around line 174:

      Unknown directive: =param

    Around line 181:

      Unknown directive: =param

    Around line 188:

      Unknown directive: =param

    Around line 195:

      Unknown directive: =attr

    Around line 202:

      Unknown directive: =attr

    Around line 210:

      Unknown directive: =attr

    Around line 218:

      Unknown directive: =attr

    Around line 226:

      Unknown directive: =attr

    Around line 234:

      Unknown directive: =attr

    Around line 242:

      Unknown directive: =method

    Around line 258:

      Unknown directive: =method

    Around line 270:

      Unknown directive: =method

    Around line 282:

      Unknown directive: =method

    Around line 294:

      Unknown directive: =method

    Around line 306:

      Unknown directive: =resource

    Around line 315:

      Unknown directive: =resource

    Around line 324:

      Unknown directive: =resource

    Around line 333:

      Unknown directive: =resource

    Around line 342:

      Unknown directive: =resource

    Around line 351:

      Unknown directive: =resource

    Around line 360:

      Unknown directive: =resource

    Around line 369:

      Unknown directive: =resource

    Around line 378:

      Unknown directive: =resource

    Around line 387:

      Unknown directive: =resource

    Around line 396:

      Unknown directive: =resource

    Around line 405:

      Unknown directive: =resource

    Around line 414:

      Unknown directive: =resource

    Around line 423:

      Unknown directive: =resource

    Around line 432:

      Unknown directive: =resource

