New Subscriber with Basic Auth

[dj_thossi]

I currently try to set up my first subscriber. My wesite is not Live yet. So there is an basic auth set up for my domain.

Now I tried to set up my first subscriber.

In Endpoint URL I put URL which included a Basic Auth as described in this post http://serverfault.com/a/371918/316948

But when I try to save the form I see following error: URL is not a valid URL

Can you please give me the opportunity to add subscriber URLs with Basic Auth.

All the best

dj_thossi

Even here I'm not allowed to have URLs with basci auth. So please see link on how I put them together.

[JeremiahFitbit]

Hi @dj_thossi,

At this time, we do not have plans to support Basic Auth, but we appreciate your feature suggestion and will keep track of similar requests.

[dj_thossi]

Hey.

Thank you for your reply.

Do you have any idea on how I'm suppose to build the subscription part of my project? By German regulations I'm not allowed to have any endpoint public accessable yet because my preoject is collecting a lot of health data from any kinds of sources.

Do you see any other way to make German regulations happy and keep working on fitbit API or do I need to exclude fitbit from list of supported devices?

Any help appreciated.

[JeremiahFitbit]

The notifications themselves only contain the user id, the date, and the type of data changed—not the data itself. I'm not familiar with German regulations, but Fitbit has many HIPAA compliant customers using the Subscriptions API.

Subscriptions API security features:

• You can use HTTPS for encrypted communication.
• The requests are signed, so you can verify the request is authentic.
• You can use FCrDNS to verify the request came from Fitbit's servers.

If you have additional security requirements, you may just have to poll for data instead.