Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Private endpoints may need additional authorization #36

Closed
Henry-Sarabia opened this issue Feb 23, 2019 · 3 comments
Closed

Private endpoints may need additional authorization #36

Henry-Sarabia opened this issue Feb 23, 2019 · 3 comments
Labels

Comments

@Henry-Sarabia
Copy link
Owner

There may be an additional required header to be sent in each request for pro and enterprise tier users. If this is the case, the auth token must be supported in the NewClient function or another function entirely.

@Henry-Sarabia
Copy link
Owner Author

Because I don't have access to a Pro tier account, I can't check whether or not the private endpoints will work without the additional auth token. For now, I will be leaving the private endpoints as part of the package until I or another user can verify their behavior.

@ghost
Copy link

ghost commented Nov 24, 2019

is this still an issue now that everyone has been bumped to pro?

@Henry-Sarabia
Copy link
Owner Author

You're right, it's no longer an issue. Thanks for the heads up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant