-
Notifications
You must be signed in to change notification settings - Fork 21
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
Custom Endpoint #62
Comments
No plans, but would welcome a proposal or just a little bit more info about what this actually means in practice. |
Sure, this would be allowing the entering of either a custom base url rather than 'https://API.geocod.io/v{api_version}'. There are instances where companies have their own base url API and also instances where you would want to hit the HIPAA compliant base url ('https://api-hipaa.geocod.io/v{api_version'). Let me know if that makes sense. |
Documentation is the problem here! The client already supports both custom endpoints and the HIPPA compliant endpoint. pygeocodio/src/geocodio/client.py Lines 62 to 70 in 077a486
|
Oh great, thanks! |
Are there any plans to add an option for custom Endpoints when connecting, so that we can leverage hipaa compliant datasets?
The text was updated successfully, but these errors were encountered: