![]() ![]() T = None # or handle error in a different way Hour, min = get_hour_min(oups(), oups(), oups()) Hour, min = get_hour_min(matches, matches, matches) Matches = re.findall(pattern, date_string) Xml = generate_xml_tracking(tracking_numbers) :return url: str tracking url for calling the USPS API :param: tracking_numbers - list of strings of tracking numbers """generate the USPS tracking request url Here's how I'm currently forming the XML request with Package Track API: from lxml import etreeĭef generate_url_tracking(tracking_numbers: list) -> str: Long-term solution (in progress pointed out that I should use the Package Tracking “Fields” API instead of the Package Track API. I've tried forming the request in Python and with Lob's USPS workspace and both XML responses lack the TrackSummary child elements. Is there an option when making the request to return these helpful XML child elements? I couldn't find one in the documentation and the sample responses I've seen all contain these child elements. The problem I'm trying to solve is obtaining the date from the TrackSummary data, which now requires regex since USPS's API is not returning an EventDate child element. This can be reproduced with Lob's USPS Postman workspace Shipping Label Created, USPS Awaiting Item, December 21, 2022, 2:16 pm, DALLASTOWN, PA 17313 USPS picked up item, December 21, 2022, 2:37 pm, DALLASTOWN, PA 17313 The item is currently in transit to the destination.Īrrived at USPS Regional Facility, December 23, 2022, 4:49 am, WEST PALM BEACH FL DISTRIBUTION CENTERĭeparted USPS Facility,, 5:58 am, HARRISBURG, PA 17112Īrrived at USPS Regional Origin Facility,, 10:12 pm, HARRISBURG PA PACKAGE SORTING CENTERĭeparted Post Office, December 21, 2022, 4:34 pm, DALLASTOWN, PA 17313 ![]() Your item departed our WEST PALM BEACH FL DISTRIBUTION CENTER destination facility on Decemat 12:40 pm. However, when performing the call, the actual XML response lacks these children elements within TrackSummary: In USPS's Track and Confirm API documentation page 19, the sample response shows with child elements (, , etc.): Worst case, I can use regex, but was wondering if there was a way to receive API responses as showing in USPS's documentation. The actual format makes it difficult to extract the event date since there is no EventDate XML element. USPS's tracking API is not returning responses in the same format as their documentation. Summary (added 12/24/22 for clarification): Postal Inspection Service rolled out a smishing awareness campaign on its public website.Īlerting customers to potential fraud helps protect their personal information and preserves the Postal Service’s brand, reputation, and customer loyalty.Please see the temporary solution at the end. We reviewed Postal Service social media channels as well as and found that at the time the Postal Service had not provided any public notification of this campaign. Postal Service, OIG auditors examined the Postal Service’s response to the attack. In our recent Management Alert, Active Smishing Campaign Masquerading as the U.S. Usually the message tries to get the target to reveal personal information, such as passwords or credit card numbers, or to convince the recipient to click on a link that installs malware.ĭuring an audit of the Postal Service’s social media activity, the OIG uncovered a smishing campaign which involved a third party posing as USPS, claiming to have a link to information about a package. What’s smishing? A fraudulent text message pretending to be from a reputable source – your bank, for example, or the U.S. Telemarketing brought robocall scams, the growth of email brought about phishing, and now, as more companies communicate with customers through text messages, comes… smishing. ![]() New types of communication channels bring new types of deception. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |