Open Statsguy808 opened 3 weeks ago
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. Edit: whoops see HIPAA enabled code on here but no custom.
Documentation is the problem here!
The client already supports both custom endpoints and the HIPPA compliant endpoint.
Oh great, thanks!
Are there any plans to add an option for custom Endpoints when connecting, so that we can leverage hipaa compliant datasets?