Ok. So I want to use the Adwords API, but would prefer to avoid paying (considering the volume of requests I'd be doing). Since they're probably changing adwords interfaces soon (the beta version), I ruled CURL out since they'd break all the regular expressions anyways.
Here's what I've tried so far.
Anyways...
So I figured that adwords editor (desktop) was probably a good bet. Dug in all morning with a debugger and disassembler.
So more or less I'm in a rut, and can't get past where I am. Anyone here have experience or ideas?
Here's what I've tried so far.
- The whole mother fucker transmits data over SSL, so sniffing is out.
- The "proxy" mode in adwords editor doesn't work (can't request data) if you use the proxy option. So man in the middle is out as well.
- Certificate doesn't validate using socksifier/local socks proxy.
- Tried fudging the DNS so adwords.google.com pointed to localhost, then set up a reverse proxy (that can decrypt SSL) running on localhost:443, forwarding to the adwords https IP. Once again, no validation.
Anyways...
So I figured that adwords editor (desktop) was probably a good bet. Dug in all morning with a debugger and disassembler.
- Their app is quite obviously using CURL and the adwords API itself. Presumably without charges.
- I'm good enough at reading the debugger data to get the gist of what's happening in there, but not good enough to emulate it
- ape.dll seems to handle a lot of the requests. It's wherre you'll find all the different variables and API post locations
- It's running a modified version of a browser in it, so there's a lot of junk data to navigate around.
So more or less I'm in a rut, and can't get past where I am. Anyone here have experience or ideas?