Solved with a lower level method, api_query:

#! /usr/bin/env perl
use Moo::Google;
use Data::Dumper qw (Dumper);

my $gapi = Moo::Google->new(debug => 0);
my $user = 'me@gmail.com';

$gapi->auth_storage->setup({ type => 'jsonfile', path => 'config.json'
+ });
$gapi->user($user);
$gapi->do_autorefresh;

$res = $gapi->api_query( {
    httpMethod => 'get',
    path => 'https://people.googleapis.com/v1/people/me',
    options => { personFields => 'emailAddresses' }
});

print Dumper $res;
[download]

I've made a little headway with this:

#! /usr/bin/env perl
use Moo::Google;
use Log::Log4perl::Shortcuts qw(:all);
use Data::Dumper qw (Dumper);

my $gapi = Moo::Google->new(debug => 0);
my $user = me@gmail.com';

$gapi->auth_storage->setup({ type => 'jsonfile', path => 'config.json'
+ });
$gapi->user($user);
$gapi->do_autorefresh;

my $r1 = $gapi->People->People;
[download]

Now I'm trying to figure out how to use the get method on $r1 to pull up my own information per the documentation.

I've tried $r1->get({ resourceName => 'people/me' })->json; but the resource is not found. I also tried with $r1->People->get({'resourceName'  => 'people/me', 'personFields' => 'emailAddresses'})->json; but still no dice.

So, I've been able to make some more headway on this by delving into the code of Moo::Google::Client.pm. There is a method in that module called build_http_transaction. The method passes a $path scalar to a build_tx subroutine in mojolicious. The $path scalar is set by inspecting Google's discovery api and has the value of https://people.googleapis.com/v1/{+resourceName} for the API call here. If I hard code the path to:

So now the question is, how do I make the call via Moo::Google so that {+resourceName} in the path gets replaced with people/me? Maybe this is impossible with Moo::Google?

NB - Steve Dondleyhas copied Moo-Google into the cpan WebService::Google namespace. It should be noted that the code as of writing this is not yet ready for prime time but Steve is working on it so I am hopeful that it becomes usable soon.

If looking to use this as a generic Google API interface be warned that although the agent works well for handling to OAUTH tokens, the dynamic classing isn't really usable except for the Calendar API. There is a lower level method that can be used to construct the endpoints and do REST directly which is really the only way you should expect to use this at the moment. The idea of autoclass generation for the API's based on the Google API discovery endpoints is a kinda cool ambition but it seems to break down quickly with the current implementation as only the top level methods can be used.

An alternative approach for those seeking to make extended use of the Google API's might be to use the swagger specs as per https://github.com/APIs-guru/openapi-directory/tree/master/APIs/googleapis.com with something like Mojolicious::Plugin::OpenAPI as described at https://mojolicious.io/blog/2017/12/22/day-22-how-to-build-a-public-rest-api/

If anybody goes down that path I'd love to here on the level of success. For my use cases I'm using the low level methods in my own version of WebService::Google::Client for GMail, GMB, Sheets etc so if anybody needs a hand on this front feel to reach out.