-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support for Fedex Trade Documents Upload API #9
Comments
You can also override the baseUri of the provider, which is probably going to be the easiest thing here, rather than spinning up a whole new provider, or adding a conditional for which API to use. Particularly if the auth is all the same. {% set data = craft.consume.fetchData('fedex', 'POST', 'documents/v1/etds/upload', {
base_uri: 'https://documentapi.prod.fedex.com/',
}) %} |
Hi @engram-design thanks a lot, so would you say something like this should work? Because server is sending me back a 500 (see 500 error below)
(I've also tried without the The 500 error:
For reference, this works:
|
Ok so I had a dig in the code, and essentially this bit here is missing the 'multipart' right? If I add in these lines this bit of code:
and in my call:
then it seems to work! |
Ah, good call. Yes we actually need to implement the shortcuts that Guzzle normally does, like Just added that in verbb/auth@d5e9c1e |
@engram-design thanks! struggling with my |
Yeah, you'll need to manually include the auth package via |
This works great FYI - fine to close for me |
What are you trying to do?
Hi there,
Thanks a lot for adding the regular Fedex API. Turns out they have another API called Trade Documents Upload API and it has a different URL:
https://documentapi.prod.fedex.com/
and then endpoints:
for documents: documents/v1/etds/upload
for images: documents/v1/etds/upload
As far as I know, auth etc works like the other Fedex API.
Thank you!
What's your proposed solution?
Implement the Fedex Trade Upload API or add an option in the regular Fedex one
Additional context
No response
The text was updated successfully, but these errors were encountered: