You can garner yourselves an AuthSub token, stick it in a system property or db record and re-use to your heart's content. Only one company-based gbase account necessary (at least recommended). You can get a second account for production and get another token and away you go. (This is just an inhouse solution, though moderately easily extended to the outside.)
On Oct 3, 8:43 am, "M@" <[EMAIL PROTECTED]> wrote: > I'm playing with a couple of google API's and am wondering if there's > a "Industry Standard" or "Best Practice" around acquiring API keys for > an organization. For R&D I'm using my own account, but what are other > developer's doing when they set up production level systems that they > anticipate they may not always be the primary developer for? I.e. > what google account should be used for a company-wide API that > multiple developers may be responsible for. > > M@ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Base-data-API?hl=en -~----------~----~----~----~------~----~------~--~---
