Company Officers API 401 CORS Issue

Hi @MArkWilliams ,
could you please let us know if the problem is identified and for fix.

@MarkWilliams If you want a demo of the problem, use the refresh icon on this page with the F12 del tools window open:
https://www.myeventflo.com/crisp/compare.aspx
(green circle arrow buttons)
If I remove the fetch_officer_data() function I get company and PSC data just fine. All three fetch functions use the same requester function sendRequest() which has
var headers = new Headers({
‘Authorization’: 'Basic ’ + apikey64,
‘Content-Type’: ‘text/json’,
‘Origin’: ‘https://www.myeventflo.com/
});
const options = {
method: method,
headers: headers,
mode: ‘cors’
};

Hi @MArkWilliams ,

Could you please check if the change implemented as per below link causing an problem on this current ongoing issue.

Hi @MArkWilliams,

Could we please request an update on this? Has there been any progression with the investigation?

This issue is causing significant issues with our business, so any update would be much appreciated.

We appreciate you taking the time to look into this.

Thanks again,
Ed

Hi @MArkWilliams is there any update on this issue yet?

Thank you,
Ed

2 Likes

Hi @MArkWilliams

Has there been any update on this? This issue is having a large impact on our operations so any update would be much appreciated.

Thank you,
Ed

@MArkWilliams do we have any update on this? we have had to turn the API off to get around this issue which has been like this since April

Hi @MArkWilliams. We to are waiting for an update. This has been an issue for a while now.
To confirm, this was first noticed by us 9th April

Thanks.

Hi @MArkWilliams,

Just following up. Has it been confirmed that the behaviour for calling this API has changed?

Thank you

We have now found the issue and are looking at a fix.

3 Likes

Hi @MArkWilliams ,
Thanks for the response. could you please advise further update on the fix and timelines to resolve.

Hi @MArkWilliams,

Good day! We would like to inquire on more details regarding the fix you plan to implement on your end. This is just to make sure that the change we are currently making will still work even after your team applies the fix. We are trying to future proof our product for the features that use the affected APIs. Thank you.

Regards,
Irvin

A solution is still being worked on, but I do not have any dates yet.

Hi @MArkWilliams ,

Good day. I hope this finds you well. Is there an update now on the solution your team is working on for this issue? Thank you.

Regards,
Irvin

1 Like

The work is ongoing and the proposed solution is currently undergoing testing.
As soon as its ready to go live it will.
We will obviously let you know when that is imminent.

Hi @MArkWilliams ,

Thank you for the updates. Apologies for pestering you on this. Our clients are pressing us for ETA. Looking at the current state of the fix, would you be able to estimate if it is possible for the fix to be completed by the end of this month? Thank you.

Regards,
Irvin

Hi @MArkWilliams ,
could you please advise us with latest update on this with testing result and when it is planned to go for live.

@MArkWilliams Could we get an update on this please?

A fix has gone in for this issue.
If you are making CORS requests you will need to ensure the api key that you are using has your site in the js_domains array.

Thanks Mark, we’re up and running again now. So very many thanks to the team for their work on this.