Restriction of API Registration

[zaplabsdev0]

We would like to see a feature where you can choose to expose/conceal the ability to register to a subset of users. This would better support B2B applications as it would only permit partner registration. Possibly adding a UI for review of registrations before the API is made available.

[afterthought]

We have similar requirements as this is for internal use mostly. It would be nice if API's could remain hidden until a user is signed in.

[MynockSpit]

What do you guys think of either of the solutions Trial-in-Error posted on #163 (comment)?

[batjko]

Similar use case here.
We are a data provider to other businesses and currently manually expose and document APIs for them, pre-generating and sharing their credentials.

None of our APIs are meant to be public, unless we authorize it on a case-by-case basis.

So our ideal scenario would be to set conditions for the registration.
For example:

• Authorize the customer's email domain (e.g. *.acme.com)
• Authorize designated client developers by sending them registration invites to their inboxes (which of course would have to be pre-shared with us by that company)
• Authorize the customer via some pre-shared secret or Activation code.