From what I learned so far the FedEx require each customer to sign up for FedEx Web Services which is very developer specific and not quite obvious for certain customers.
I'm curious if there is a better way to connect FedEx services with a hypothetical SaaS product?
You need to become a FedEx Certified Developer. It's a very time-consuming process. When you request web service credentials they ask very specific questions about inside/outside development. Based on these questions you should be able to get in contact with the proper department.
Related
I'm a solutions architect for a fintech company, We have a lot of our clients using your software and I was wondering if it's possible to get a sandbox account to your API.
I'm exploring accessing mail (and sending mail) on behalf of other users. I have read about the graph api which would allow me also to handle chat messages later on.
I wanted to start implementing this with my personal account (#outlook.com) and followed basically this tutorial: https://cmatskas.com/create-a-net-core-deamon-app-that-calls-msgraph-with-a-certificate/ (this seems to be the same as the walkthrough in the portal)
I found questions and answers (like Microsoft Graph to send mail with Client Credential Flow (application permission) and personal account) but I do want to create a daemon app which seems not to work with a personal account (which makes sense because I could read Microsoft's end user customers data).
Furthermore, when trying to create such an app there is the following warning:
If I would create a development env for this I am still now working at a verified publisher, so I cannot develop an application to see if it fits our needs?
It is possible to have a developer sandbox from Microsoft for that purpose.
See https://learn.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program-get-started for information on this
I want to develop and publish a bot for Teams, to interface with my SaaS (I already have a Slackbot that I'm porting). I'm creating a Bot Channel Registration as per this guide and came across the choice of whether to auto-generate a new App Id and password, or manually registering one (described here). I already have an Azure AD app for my SaaS that is published to the AppSource marketplace (the integration currently mainly allows logging in with your M365 account and syncing users from AD). Is it possible, and would it make sense to use the same App ID for the bot I'm developing for the same SaaS? Or is it somehow not advisable? And relatedly, can I expand my existing listing on AppSource to also contain the new bot, or should this be a separate listing?
I noticed in the documentation for manual registration of a bot, that it says that bots only work with "Accounts in any organizational directory and personal Microsoft accounts (e.g. Xbox, Outlook.com)" - my existing app only works with organization accounts, not personal accounts (since it's a B2B app) - does that change things?
Perhaps consider the question the other way - is there any good reason TO re-use the app ? It's very easy and basically free to create an additional app, and that way you don't run the risk of possibly ending up with settings needed for one scenario that conflict with another scenario's requirements, now or in the future. Here are some other possible considerations though:
new apps require Publisher verification, since 9 Nov 2020. This won't affect you for an internal app, which can be consented to by a global admin.
If you need the user (or admin) consent for some set of privileges (e.g. delegated Graph access), then using the same app might make sense. An example, in a Teams context, might be a bot and a tab that both need to access something from the Graph on the user's behalf. You could get consent in one context, and use it to access the resources from both contexts.
In a nutshell, and especially without a really really good idea of both of your current and planned use cases, it's hard to give a really solid 'yes' or 'no'. My gut says go with a separate app for a separate, unrelated scenario though.
Reusing the same appid against any other B2B won't create any problem. Being said that you can't use the above app if you're planning to implement/use BOT framework with it, as it's registered for organization only.
If you plan to create BOT related app registration then i would
suggest you to create new app registration with Organization +
personal for you scenario.
Please see the documentation and it's disclaimer:
In the above document it's pretty clear if you create any other app registration (other than Organization + personal), then the BOT will be unusable.
Hi I want to use Paypal to accept payments in my applications. I feel like I'm going around in circles. What I have gathered is that there is very little documentation and a lot of marketing guff that you need to wade through - no disrespect to anyone who has worked on it.
I've learned that the Restful APIs from Paypal are not full featured yet, and the classic APIs provide a richer set of features - and my merchant account is in Australia so I don't think I can use REST APIs yet.
I've got a number of questions :
What do I need to get started ? Is it essentially formatting a payload according to the documents and calling a web service or is there more to it ?
Are there any sample .net applications that use the classic API. I may have missed something but GIT repository only seems to have REST api samples - should I get this and use classic in its place or is there more to it ?
Should I be using the SDK at all ? I checked in Nuget and there are a number of SDKs - the asp.net -http://www.asp.net/web-forms/overview/getting-started/getting-started-with-aspnet-45-web-forms/checkout-and-payment-with-paypal and it doesn't talk about the SDKs ??
If I am to get the SDK which one should I start with for Classic, I'm assuming I only need the SDK for the respective functions I need. For example there is a Merchant SDK and Payments Pro SDK which has the same information on www.paypal.com/SDK
What I want to be able to do is the following:
Accept Credit Card and Paypal payments on my wedapp
Do Adaptive Payments
Establish Recurring Payments after a Credit Card and Paypal Payment
Do PreApproval
Provide Express Checkout as per Paypal requirement
Please help, there appears to be a lack of getting started guides for Paypal and MVC. If anyone has any samples that would be fantastic!
I can certainly help you with your Express Checkout requirement, and in shedding some light on the complexities of interfacing your application with PayPal.
This .NET SDK offers full support for Express Checkout functionality, as well as providing a concise readme that outlines how Express Checkout works at both high, and more precise levels of abstraction.
In terms of Express Checkout, there are 3 main terms that you should familiarise yourself with:
SetExpressCheckout
Establishes a PayPal session based on Merchant credentials, and returns an Access Token pertaining to that session.
GetExpresscheckoutDetails
Returns a definitive collection of metadata that describes the PayPal user (name, address, etc.).
DoExpressCheckoutPayment
Collects the payment by transferring the transaction amount from the User's account to the Merchant account.
I want to fetch real-time data from my Quickbooks Online edition's (India) account to display customer details like Open Balance, address etc. on my PHP website.
What is the best way to go about fetching data from Quickbooks Online Edition -
Do I follow the instructions in http://wiki.consolibyte.com/wiki/doku.php/quickbooks_online_edition#connecting_with_the_hosted_model_of_communication ? But this requires a website with SSL certificate.
Do I create a Intuit Anywhere app ( https://ipp.developer.intuit.com/0010_Intuit_Partner_Platform/0025_Intuit_Anywhere/1000_Getting_Started_With_IA ) and then use IDS (Intuit Data Services) to fetch the required data using the API?
Can I use the PHP devkit ( https://code.intuit.com/sf/frs/do/viewSummary/projects.php_devkit/frs ) and feed my credentials directly to the code and access my Quickbooks account's data?
Do I use qbXML (which however does not seem to be the recommended method)?
Or is there a better solution?
Thanks in advance.
First, a disclaimer - if you're using the India version of QuickBooks Online (http://www.quickbooksonline.in/) you'll likely find that nothing works at all. Currently, Intuit does not officially support ANY non-US version of QuickBooks Online (QuickBooks for Windows non-US is supported via qbXML) for integration, regardless of which method you go with. It might work... but I doubt it.
With that said... generally speaking:
If you're building a SaaS application and trying to allow your
end-users to connect their QuickBooks accounts to your app, use
Intuit Anywhere.
Otherwise, if it's a custom/one-off/internal application, and you hate your life, use HOSTED mode via https://appreg.intuit.com and the HOSTED instructions on our QuickBooks integration wiki (HOSTED mode is notoriously unreliable and difficult to get going due to reverse DNS checks, a very specific certificate format, lack of working example code, bugs on Intuit's end, some serious nasty-ness hooking the certificate up to your .NET HTTPS request, etc.).
Otherwise, if it's a custom/one-off/internal application, and you DON'T hate your life, use DESKTOP mode via https://appreg.intuit.com and the DESKTOP instructions on our QuickBooks integration wiki.
None of the APIs allow you to just pass your credentials in and get access - you'll always have some sort of API token to deal with (a "connection ticket" for qbXML, or OAuth for Intuit Anywhere).
If you build for Intuit Anywhere, you'll use IDS XML. Otherwise, you'll use qbXML.