>>Thanks. What I need to do right now is POST to a website, passing some JSON, and get JSON back as a response.

The transfer part should be trivial whichever route you take. For JSON, you *could* roll your own but Rick includes quite a bit of JSON stuff and Craig Boyd also documented a JSON class at his site.

>>When I looked into the question of texting a year or so back, Twilio seemed to be the way to go. At the time, it appeared to me that on the VFP side, I could either use the VFPX TwilioX or Chilkat. The client decided not to implement then. Looking back at my notes, I see that I didn't think wwIPStuff could handle this. Wonder if that's actually true.

Twilio appears to be a frontrunner. A quick check confirms the Twilio API is fairly simple REST, so when the time comes you could use that VFPX version, or to avoid overhead from the quite big libcurl.vcx (and vfp2c32.fll) you could just roll your own message and submit it.

If exact txt timing is not crucial (e.g. txting out "your service is due") then you might still consider the emailed txt option. It's always going to be regional via your cell provider with txts deducted from an existing quota, so no additional cost. Probably not quite as good for urgent comms since emails are allowed to be tardier and less reliable than an API hit.