Developer API question

C2
1

I made a call to www.collective2.com/cgi-bin/signal.mpl? … for a ‘cmd=getbuypower’ call and it gave me a 302 redirect to preview.collective2.com.



Should I be using preview.collective2.com in all my cmd HTTP GETs rather than www.collective2.com (which is what the docs currently say) ?



Thanks,

David

2

David -

Sorry about that. We had started redirecting all signal traffic to the preview server via the www webserver, not realizing that the redirect would break some API clients. This should now be reverted to the old behavior.

Thanks,

Matt Vella

3

Thanks, Matt. So going forward, I assume I can always depend on the URL being www.collective2.com?



Thanks,

David



4

David-



We would in fact prefer if developers use the API at signal.collective2.com. It is an alias for www.collective2.com currently, using this allows us to point it elsewhere in the future. In essence, it provides us the ability to flexible and scalable while keeping a consistent URL for developers.

Look for this change in the next version of the API docs, and go ahead and start using signal.collective2.com if you can.



Thanks,

Matt Vella

5

By signal.collective2.com, do you mean http://www.signal.collective2.com?



Cliff

6

Actually Matt means: use http://signal.collective2.com for API calls. (Notice no www.)



API users should begin to transition to this URL. The old www.collective2.com will continue to work just fine, and we have no intention of dropping support for API clients at this address, but it would be better if we could begin to transition API usage to a separate address.



An example of what we are taking about:



http://signal.collective2.com/cgi-perl/signal.mpl?cmd=blahblah



Obviously none of this applies to you if you are not a programmer and are not using our API to submit your signals to C2.



Matthew

7


Thanks, guys - I’ll switch to signal.collective2.com from now on.



Have you thought about using HTTPS (SSL) instead of HTTP? It would be good to not have to pass my password in the clear. I think most trading APIs use HTTPS (e.g. Ameritrade, etc.) - just a thought.



David



8

David - you can in fact use HTTPS with the signal.collective2.com URL, and I would recommend it. Let me know if you have any problems using it.



-Matt