Civicrm Wordpress error 403 when putting in Private token api key unable to connect to eventbrite

[chris453]

My issue is even though I have

• set up webhooks to go to my site and ( they send to each other )
• checked my website /civicrm/api event queue and see that I am receiving the requests
• made a api key in event brite to my website as the Application url ( is this step correct? )
• set OAuth Redirect URL as blank in eventbrite
• on a live server (dream host is hosting my website ) which is accesible from the internet

I am still getting this error on my civicrm when i submit the private token of my api

Error establishing webhook configuration via Eventbrite API. Eventbrite said: 403: NOT_AUTHORIZED: This user is not able to use legacy user endpoints, please use the organization equivalent.

[twomice]

I'm seeing some indications that the api used for establishing webhooks (and some other EB apis) are unsupported after June 1, 2020:

• https://jsapi.apiary.io/apis/eventbriteapiv3public/reference/webhooks/create/create-webhooks-deprecated.html (references the OP's error message)
• https://www.eventbrite.com/platform/docs/changelog documents various specific deprecations.

@josephlacey or others, are you aware of organizations still using this extension and having success/failure that might be related to any of this?

[josephlacey]

Unfortunately, no. Though I might not be the best reference here. The one instance using this extension that I know of is using Drupal (maybe not relevant) but also hasn't integrated with EventBrite recently. Everything's been postponed with the pandemic.

[twomice]

@chris453 It sounds like you're saying you:

1. set up the webhooks manually, and
2. observe that webhooks notifications are being received at the CiviCRM end.

Is that correct? And if so, are you seeing EventBrite data actually being populated in CiviCRM? If so, it might mean the webhook-related error message could be ignored, as long as everything else is working as designed.

Your thoughts / findings?

[chris453]

@twomice
I setup the webhooks as you mentioned in this post #11
Log into Evenbrite and then visit https://www.eventbrite.com/account-settings/webhooks . There should be two webhooks there, pointing to your site: Action "order.updated" pointing to Payload URI "https://[yoursite.com]/civicrm/eventbrite/webhook", and Action "attendee.updated", also pointing to the same Payload URI. If these don't exist, you should see some message about it in item number 1 above.

2. I observed the webhook notrifications by doing this step as you mentioned as well
   Did your CiviCRM site receive the webhook notification? All Eventbrite webhook notifications are stored in a queue for processing later by the appropriate Scheduled Job (see below). This queue is stored in the database table civicrm_eventbrite_queue. You can examine the contents of that table directly through SQL, or you can use the CiviCRM API explorer ([yoursite.com]/civicrm/api) to run the EventbriteQueue.get operation and thereby retrieve a list of all queue entries. If Eventbrite sent the webhook notification (see item 4 above), but the webhook notification is not contained in the queue, this will prevent data syncronization. Please let me know if that's the case.

i get this back when i run EventBriteQueue.get

"id": "6",
"created_date": "2020-08-05 16:26:29",
"message": "{"config": {"action": "attendee.updated", "user_id": "70100545771", "webhook_id": "2342822", "endpoint_url": "(my site)/civicrm/eventbrite/webhook"}, "api_url": "https://www.eventbriteapi.com/v3/events/113543503676/attendees/1974961751/\"}",
"status_id": "1"

I am also not seeing the eventbrite data being populated in CiviCRM

[twomice]

FYI, I've updated the README file with a note on project status. Because we don't use EB here, it's hard for me to keep this up to date, though I'm hopeful some EB user organization will be interested in sponsoring the work to get it working agian.

NOTICE of project status

This project is known to have significant issues with the current EventBrite API.

Although it worked well when first released, EB has made changes to their API, and this extension is very likely not to work completely, or perhaps in any usable way.

If you're a current EventBrite user who'd like to help sponsor the work needed get this working again, please contact us directly via https://joineryhq.com/ to discuss your needs.