New V2 API Alpha Release
Developers,
TextMarks is pleased to announce the alpha release of our new V2 API:
http://alpha.api2.textmarks.com/help/
This new API is designed to replace our more basic existing API, which will be phased out over time.
Much of what’s new is based on the excellent feedback we’ve received already from developers like you. Your comments are appreciated and will help shape the final product to the be as useful and clear as possible. Feel free to leave comments on this blog entry or send to our developer support.
Note: While this release is fully functional, it is an alpha release and as such is subject to change (including but not limited to error codes, argument names, method names, response formats, etc.)

March 27th, 2009 at 9:05 pm
so i am confused as to how this works because i can’t find anything that shows a api that we can download so how can we do this without downloading a new api file?
am i missing this or is it just not here?
March 27th, 2009 at 9:48 pm
@Jared,
The new V2 API does not yet have client libraries publicly available. You may still interface with the API using standard HTTP requests, but you will have to write your own client code for now.
We will likely release PHP and Python client libraries first.
Meanwhile be sure to try the “TEST” box on each API method documentation page. You can make direct API calls from your browser and inspect the results. This is a good way to familiarize yourself with the new API.
April 21st, 2009 at 11:06 pm
It would be nice if an API method like invite_to_group() would echo back the number/user sent with the request so I can tell what the request was for. When I submit a new number, I just get OK. When I submit a number with a pending request, the number is returned back, but only in the error message.
April 22nd, 2009 at 11:23 am
@John S.,
In which API methods specifically are you interested in seeing this extra info?
Also, can you say in what context would you not know what the request was for and would need this info?
May 15th, 2009 at 5:01 pm
[...] The old commands and terminology are still valid, but you may see some of these new terms in system messages, on our site, and in our new V2 API. [...]