Why messages are being send to Canada even though it's not selected in Geo permissions?
I have only US and Poland selected but still, messages to Canada are delivered. I can see they have the same country code- is there a way to fix it?
Related
I am developing a mobile app and website that allow users to advertise their items only in the UK. However, I don't want the return address to show the full address of the seller on the advert but instead should show the town and the city
For example, 395 Frances Street, London, SE18 5JU, England, UK. This address is in Greenwich town. I just want the location on the advert to show only the town and the city. For example (Greenwich, London)
I mean I would like to restrict the address not to show the full address but specific town and city. Please what is the best solution and how do I achieve this. any suggestion would be appreciated.
You can use Geocoding API if you have the street address and check the "address_components" in the response or use the Places API to request Address Components about the place (Place.Field.ADDRESS_COMPONENTS if using the Places SDK for Android and GMSPlaceFieldAddressComponents if using the Places SDK for iOS). Both will return the address broken into components so you can select which components to display. Each component type is explained in documentation though it may take some experimentation to know which administrative_area_level_N corresponds to the concepts of "town" and "city" in your area.
I have an implementation for shipping working for US shipping, however I am unable to get this implementation to work with international shipping. I am using the shipping codes 07, 08, 54, and 55 but am getting the error
"111210 The requested service is unavailable between the selected locations.".
I dont get this error when I enter a ship to address in the US. I have tried Spain and Mexico.
Does the rates API support international shipping? Is there anything different that needs to be done or passed in to get international shipping rates to work?
After posting my comment to OP I found the solution I was looking for. In case anyone else encounters this post while researching this problem here's what worked for me:
In your request, for Service Code, use one of the Worldwide codes. I used 65 (UPS Worldwide Saver) for my specific needs.
Hope that helps someone in the future!
I have been trying out the travel API from sabre, been testing APIs (for example InstaFlights Search or destination finder) and it works only for US cities (departure and destination). I've been testing them on sabres website (so this has nothing to do with my code). I don't assume that sabre API is only for US domestic flights as that would be too strange, so does anyone know why I'm getting 404 when I try to put a non-US city as departure or destination?
Thanks a lot!
EDIT:
Random international flights options do work and some don't.
For example MUC-LHR ( Munich to London) works when I change the point of sale country to DE but doesn't work for MUC - JFK for example.
Are you hitting CERT or PROD? Not all of Sabre content is available in CERT, so that might be why you're seeing such odd results.
I have created an application that that sends error notifications to some mobile numbers located inside and outside of the United States via Twilio.
Inside the United states I get the expected results. The message shows that it is coming from my Twilio assigned phone number. However, when I test to an international destination; the results are unpredictable.
Sometimes I receive the message "from" a long number that is almost never the same twice. Other times I receive the message "from" a meaningless and sometimes strange "short code" that changes frequently as well.
How can I prevent this unwanted, unpredictable behavior?
Twilio Customer Support here - this is not really a stack overflow question as its to do with the way carriers send SMS in certain markets, but if you write into the help#twilio.com we'll explain in more detail.
Different countries actually have different policies about sender IDs. In some countries you are able to deliver A2P traffic only from alpha senders, for example. In other countries you might be able to send messages only from a local longode sender ID or from a shortcode like in USA. There are also often different routes available which may support different features. If you would like to test out features of the route your current SMS supplier has, you can send test SMS messages on mobile test numbers of telqtest.com
I want to validate that the postal address filled in by a user is correct.
Assuming that we have the fields street, street_number, postal_code, city and country
How can show errors when the user, types in that his country is France and is city is New York?
or
How can I detect that a postal code doesn't correspond to the city?
Is there a strategy to address this issue with Ruby On Rails or shall I just trust the user entries ?
There are several companies that publish US ZIP code directories, typically not terribly expensive, and some even come with lat/lon data. This is the most common way of validating city and state in the US or North America. Worldwide postal codes to country and city is likely to be a harder problem, or at least a more expensive one.
Another approach would be to use the Google Maps API, perhaps in conjunction with the data you can get from location-aware browsers (all modern ones). To be honest, it's been a while since I have used the API, but seem to recall you can get pretty detailed information given a lat/lon. Google now charges for high use of the Maps API, but if your site has even moderate traffic, you're probably still in the free zone.
At some level, you'll have to trust users. I remember a while back we found anomalies in user reported zipcodes in our database -- seemed like everyone lived in Beverly Hills, CA. This was around 2000, when the original version of the TV show "90210" was still around -- that's the zipcode :-).
Have you considered just a jQuery plugin to verify addresses for you? It's free for many users, up to 250 lookups/mo, and is always current (no need for you to maintain a database).
Incidentally, I work at SmartyStreets. There's also a ZIP code API to look up if cities match ZIP codes and vice-versa. Either way, we've put a lot of effort into making the user experience positive, even when the address they type isn't totally valid.