I'm having troubles buying FedEx shipping label through EasyPost.
I was trying to buy label for FedEx International Economy service and received the following error message from EasyPost:
Shipment: shp_XXX, message: Validation failed: Predefined package Invalid predefined package type.
I didn't set any predefined packages, maybe this is the problem and I must enter predefined package along with weight only?
Please help me out.
Thanks
Can you post your call?
It looks like you're included a predefined_package which is only available for another carrier.
Related
I want to export everyone who has reply stop (opt out) for my messages. I see that my options are
API. However, through the API I can see that I get everything in pages of 50 messages, so I have to go and do a lot of code to go page by page, message by message just to check if the content is stop. Seems a bit unnecessary for a 1 time job.
From the console in my account, however when each time i try to filter on status received I get the following error, and when I dont filter I get error:
Your export request has more than 10,000 records, please filter your results and try again.
Surely there must be an easy way that I can get all the list of numbers that had opt out?
This answer above is not strictly true as of October 2020. Twilio now has an "insights" dashboard that allows you to view and download "Opt outs Received". When you click on that dashboard you are able to see and download the information.
It is under: Programmable Messaging -> Monitor -> Insights
Our account has "Opt-Out Management" enabled and this addition has been a game changer in finding out what users have or have not done in our system.
There isn't a way to export all opt-outs for LC's/TF's that Twilio maintains on your behalf but opt-outs are forwarded to your application for logging as well as added to the Twilio maintained opt-out list. Your application can keep track of the opt-outs this way. You can find more details in the Help Center article below.
Twilio support for opt-out keywords (SMS STOP filtering)
"When Twilio receives one of these replies, we will create a "blacklist" entry on our side, and then pass the message on to your webhook. Once we have a blacklist entry for a particular recipient phone number, any future attempts to message them will be met with a 400 response from our API, along with Error Code 21610 - Message cannot be sent to the 'To' number because the customer has replied with STOP. Recipients can disable this message stop, and resume receiving messages with the START, YES, or UNSTOP commands as outlined below."
Also, if you use the Twilio helper library for the respective language, it handles the paging for you, for example, for Node.js, reference.
Usage and Migration Guide for Twilio's Node.js Helper Library 3.x
"One of the biggest advantages of twilio-node 3.x is that it automatically handles paging for you! In both list and each, you can specify the maximum number of instances to grab (limit), and the page size (pageSize). The library will take care of everything else."
How can I update mail to show a "warning" message that exists on a users' mailbox as like what you see when mail is moved to the "junk mail" folder using the Graph API? See attached screenshot. Obviously, I want this message to be customised with my own text. It's not possible to update messages if they aren't draft (isDraft=false).
I dont think that Transport rules are good for us because I want to add that label after the message has arrived into the users' mailbox.
I know that its possible to add Custom Attributes to a message resource - https://learn.microsoft.com/en-us/graph/api/resources/opentypeextension?view=graph-rest-1.0
Can I utilize it? any way that you can recommend to do such a thing?
Do I need to develop any addon for that?
After speaking to the PM , there is no supported scenario to do this. If you require this feature you can make a request on https://microsoftgraph.uservoice.com/
we recently started using Twilio lookup with the Carrier Info add-on to validate phone number format and determine the number type (mobile/landline). Most of our numbers have been U.S. or UK and we haven't had a problem.
Today we encountered our first Australian number and it caused an error for the Carrier Info portion of the response, specifically code 61003, "Requirements to invoke AddOns have not been met." The basic lookup portion of the response, with country code, number format, etc., is fine.
However, when I try the same number on the public-facing Twilio web page (https://www.twilio.com/lookup) the whole lookup including carrier info works fine.
Does anyone know if there are different API call requirements for numbers in different countries? Or what else might be wrong? Thanks in advance for any help.
The answer seems to be that this was a temporary error at Twilio. After the weekend, and without any changes in my code, the same number worked fine. Twilio support said they weren't aware of any problems with the service but that they would alert the engineering team that this had happened.
According to the documentation the ApplyCheckToTxnAdd member of a CheckAdd message in the QuickBooks SDK takes an optional usemacro value. When I do this it errors with a There is a missing element: "TxnID".
This suggests to me that there is either a bug in the documentation or Web Connector or QuickBooks itself.
The business scenario I am trying to replicate is to paydown a customer credit memo by writing a check.
Any ideas?
Thanks
Mark
I'm using Quickbooks SDK v11 to integrate with a C# application. Almost everything works fine, but I have a problem with the sales tax country. I want to add customer records to Quickbooks, and I can't figure out how to do it.
To see what's in Quickbooks already, I'm using the following code snippet:
ICustomerRet ret = [My code to retrieve a customer];
ENSalesTaxCountry stc = (ENSalesTaxCountry)ret.SalesTaxCountry.GetValue();
This works fine for a UK customer, but if the customer has a sales tax country of France, the GetValue() call throws an Exception.
A poke around with Intellisense reveals that my ENSalesTaxCountry type only has three options: stcAustralia, stcCanada and stcUK - clearly excluding France.
It seems that the SDK enum supports only these three countries, while Quickbooks itself supports a whole bunch of others.
Any ideas for how to patch the SDK or otherwise get round the problem?
There's no need to rely on intellisense for documentation - you can use the IDN Onscreen Reference for a complete description of SDK queries and responses. You are obviously either using the Canadian or UK edition of QuickBooks, so be sure to check Allow CA or UK 2008+, then either CA or UK to indicate the edition you are using.
However, once you do this you will see that the only sales tax countries supported by the SDK are the Australia, the UK and Canada. In order to find out whether qbXML is returning France or other values that are undocumented, you can call the ToXmlString() method on you ICustomerRet interface. This will give you the raw qbXML. If the value "France" is there, you should be able to see it.
If you find that the qbXML is supporting undocumented countries, you can try including them in customer add requests, but you have to build the qbXML yourself and use the request processor component instead of QBFC to send the message.
You might be able to get more information about this by posting on in the Intuit Developer forums, where you will find dedicated forums for both UK and Canadian QuickBooks development. In fact there is an active discussion on sales tax countries in the UK forum right now, but you won't find it to be encouraging.