Category Archives: APIs



Using the old HTTP SMS developed by Cardboardfish, enterprise acquired by MBLox and then by

The issue: was using the httpsms.dll developed by Cardboardfish, in a .net platform running .net fx 4.5.

on 10 june 2021, the Atlas HTTP SMS Migration completed and the New FQDNs changed to new ones with http (443).

Impact MT/MO/DLR: API calls to the legacy Mblox Atlas HTTP SMS API URLs will be responded with HTTP status 302.

Client Action Required: Client applications to switchover their API calls to the new Atlas HTTP SMS API URLs below.

Please find the old and New URLs as below:

RegionOld FQDNs ImpactedOld PortsNew FQDNsNew Ports
EUsms1.mblox.com9444 (HTTPS)/9001 (HTTP)eu1.httpgw.api.sinch.com443 (HTTPS) only
EUsms1.cardboardfish.com9444 (HTTPS)/9001 (HTTP)eu1.httpgw.api.sinch.com443 (HTTPS) only
EUsms5.mblox.com9444 (HTTPS)/9001 (HTTP)eu2.httpgw.api.sinch.com443 (HTTPS) only
USsms2.mblox.coml9444 (HTTPS)/9001 (HTTPus1.httpgw.api.sinch.com443 (HTTPS) only
USsms2.cardboardfish.com9444 (HTTPS)/9001 (HTTP)us1.httpgw.api.sinch.com443 (HTTPS) only
USsms3.mblox.com9444 (HTTPS)/9001 (HTTP)us2.httpgw.api.sinch.com443 (HTTPS) only
USsms3.cardboardfish.com9444 (HTTPS)/9001 (HTTP)us2.httpgw.api.sinch.com443 (HTTPS) only

The solution is to migrate to REST API, or upgrade the dll to new FQDN.

To upgrade is needed the source files and have recompiled it.

The REST API and HTTP SMS in .net 4.5 the Webrequest must deal with https:

worked using: 
ServicePointManager.SecurityProtocol = CType(3072, SecurityProtocolType)
ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;


APIs Utils Web web services Yahoo!

Yahoo! Query Language

What is YQL?

The Yahoo! Query Language is an expressive SQL-like language that lets you query, filter, and join data across Web services. With YQL, apps run faster with fewer lines of code and a smaller network footprint.

Yahoo! and other websites across the Internet make much of their structured data available to developers, primarily through Web services. To access and query these services, developers traditionally endure the pain of locating the right URLs and documentation to access and query each Web service.

With YQL, developers can access and shape data across the Internet through one simple language, eliminating the need to learn how to call different APIs.

How Do I Get Started?

  1. Check out the YQL Console.
  2. Complete the The Two-Minute Tutorial.
  3. Read how to access YQL from your application.
  4. Get your API Keys to sign your requests if you need them.
  5. Check out the YQL frequently asked questions (FAQ) for answers to common issues.

read more »

APIs Google Google Maps API

GMaps Geocoder Accuracy and Zoom level

Geo Address Accuracy

The Google Maps API development team released a small  improvement to their Geocoding API: the ability to get the response’s accuracy level for a given address.

This feature enables applications to modify their zoom level according to the precision of the address that’s being geocoded, for example, “Paris” at the city zoom level, but “1 rue Royale, 75008 Paris” at the much more precise street address zoom level.

What the Google geocoder actually outputs (see reference) is a value between 1 and 8. And the GMaps zoom level is an integer between 1 and 19. So the question is: given a geocoding accuracy, which zoom level should I use to display the place? I didn’t find any answer to that question on the web so I decided to make up my own correspondence between the two scales.

Any such correspondence is bound to be imperfect since two different cities can have very different sizes, however the method usually outputs a decent result.

read more »