You can make it part of the specs that usernames/passwords be prompted at the time of usage rather than be given to the developers and stored in the app/database.
On Oct 8, 3:15 pm, crosby <[email protected]> wrote: > Hi, > I'm sure this has been solved by some of you out there. Thanks in > advance for your thoughts. > We are going to 3rd party develop some API tools (mostly around "get" > of structure and performance data). > I don't want to give the 3rd party developers keys to my castle, but I > need to know that they can develop and test in a sandbox which has > some of the same amounts and types of data as I have under my MCC. > > we have over 4MM words in play across 7 accounts, so some daily > reports must be broken out by account, etc. > > So, how do I get these developers appropriate access keys? > Does the sandbox provide "big" accounts suitable for testing with? > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" 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/adwords-api?hl=en -~----------~----~----~----~------~----~------~--~---
