Def been a learning experience using EB's self-proclaimed "easy API". In the EB API test environment, I get the correct result.įairly certain it's an EB issue but wanting to double check I've got everything right and the PW API isn't doing anything too clever with the $_GET vars. "There are errors with your arguments: page_size - Enter a whole number."Įven stranger is if I manually create the URL, eg $pageSize ) Įvery time I use a parameter, I get the EB error message for the last one, in the example below, the paging limit: $result = $eb -> client -> get ( $ebPath. $token = $sanitizer -> text ( $eb -> access_code ) ![]() Problem I'm having is with using parameters in the actual API, eg: ![]() $result = $eb -> get ( "/users/$ebUserId/owned_events" ) $ebUserId = $ebUser // /users/:id/owned_events/ $ebUser = $eb -> client -> get ( '/users/me/' ) $eb = $modules ( 'EventbriteAPI' )-> login () Love it!Ĭan do any of the API GET calls providing they don't include any parameters, eg: ![]() The EB webhooks are a easy-peasy-lemon-squeezy. Latest endeavour is a PW module for Eventbrite v3 API Why re-invent the wheel when there are so many great, well-supported apps out there that don't impact on the core of PW? Almost see PW as a portal. Hi, me again - queen of the ProcessWire API Wrapper.
0 Comments
Leave a Reply. |