Dropbox Extensions - Is it possible to create/publish a Dropbox Extension? - dropbox

I'm currently assigned to create a Dropbox Extension.
This is a new feature that Dropbox released last November 2018, here's their article.
I read the Dropbox API documentation. I created a Business trial account (Advance). However, there was nothing about the submission/publishing of extensions.
I also stumbled upon the Dropbox Partners Portal and successfully registered a Tech Partner Account for the company I'm working in. Unfortunately, I also did not found anything about the extensions.
I think this portal is not maintained anymore because:
General, Marketing, and Technical resources are not available. (even the Welcoming Resources also does not exist)
The copyright year in the footer also displays 2017.
There is no KYC, or some kind of evaluation process to verify if the information given is authentic.
I could be wrong though (For those who actually know, please link an article or announcement).
So is this new feature only for companies chosen by Dropbox?
Will this ever be open to the public submissions/publishing?
Or maybe this is already open to the public and I'm just looking in the wrong places?

Answered in the Dropbox Community forum:
https://www.dropboxforum.com/t5/General-Discussion/Dropbox-Extensions-Is-it-possible-to-create-publish-a-Dropbox/m-p/323180#M25931

Related

Azure API Management Developer Portal

I have a requirement to expose the APIM Developer Portal to external partners, I want the developer portal to be my one stop shop for these partners to access and learn everything they need to know about my APIs, in the main APIM Developer Portal satisfies that requirement but when I want to add new content e.g. specific design, architecture, user guide documentation etc about the API it starts to get very confusing, for a start it looks like the depreciated publisher portal (which still exists) is the only place that I can add new pages. The new pages seem very limited and clunky and cannot be amended in the new version of the portal. There is also very limited documentation outside the standard MS stuff and nearky all of that relates to amending the current pages and templates.
My site will go live at the end of the year and I don't want to find one day these new content pages missing from the portal and my supporting documentation removed.
Does anybody know where Microsoft is going with the developer portal for customizing outside outside the standard templates they offer or can anybody supply me with a link of documentation that addresses new content pages?
It looks like the depreciated publisher portal (which still exists) is the only place that I can add new pages
Yes, you need to use the publisher portal to add new pages.
The new pages seem very limited and clunky and cannot be amended in
the new version of the portal.
What do you mean by new version of the portal?
I am going live at the end of the year and I don't want to find one day these new content pages missing from the portal and my supporting documentation removed.
If your worry is that API Management will automatically remove your content because of publisher portal deprecation - you can rest assured this is not going to happen, especially without any previous notice.
Does anybody know where Microsoft is going with the developer portal for customizing outside the standard templates they offer?
There is some work planned to refresh the developer portal. Can you please elaborate more on what you are trying to achieve? What is your goal?
One can edit those pages in 2 places: Publisher Portal and Developer Portal.
In the Publisher portal you can add widgets to predefined areas on the page. For example you can add a HTML widget to the home page for authenticated and non-authenticated users. Rasmas Gude has a great article about that here.
In the Developer Portal you can change the information shown on each page by editing the template. There's a edit template icon available on the left for administrator. If you click that and then select the section you want to edit a split screen will appear below. The left have is DotLiquid markup and the right is the data model for that section. With that information you should be able to modify the page in the manner you wish.
If they are decommissioning the publisher portal, it will be enabled in the azure portal. Earlier we have the API, Products and users etc in the publisher portal. that are added in the other portal. The deprecation of the portal, dosnt mean the existing functionality will fail, which have the alternatives.

Instagram API change without warning?

I know that as of June 2016, Instagram are going to vet who can use their API, but we've noticed something has changed early.
Does anyone have any information on how the vetting process is going to work?
Take a look at Instagram platform update.
Simplified platform policy
We’ve updated our Platform Policy to
explicitly list the use cases we will support moving forward. These
include apps and services that:
Help individuals share their own content with 3rd party apps, such as
apps that let you print your photos and import an Instagram photo as a
profile picture. Help brands and advertisers understand and manage
their audience, develop their content strategy, and get digital rights
to media. Established apps in this space may apply for our newly
announced Instagram Partner Program. Help broadcasters and publishers
discover content, get digital rights to media, and share media using
web embeds. You can read the full terms here.
New review process and sandbox
We will begin reviewing new and
existing apps before granting full API access starting December 3,
2015. Existing apps have until June 1, 2016 to submit and be approved.
We are also launching Sandbox Mode, which will let you privately build
and test your apps using Instagram’s APIs as your app is being
reviewed.

Is QuickBooks API QBD V3 Really Deprecated?

I just started developing an Intuit App yesterday and was really getting going on integrating with QuickBooks Desktop. Then today I logged in to continue work and was greeted by several missing pages on Intuit's IPP site and a link that says "Deprecated QBO V2 and QBD V2,V3". The only API that appears to not be deprecated is QBO V3.
I cannot find any announcement from Intuit about any upcoming deprecation. Does anybody have any info on whether I am safe to continue developing my app to connect to QBD or do I need to talk to our accountant to move over to QBO instead?
EDIT: I have marked Jarred's answer as the accepted answer because he associated with Intuit and answers my specific situation. Also check Charlie's answer for additional details specific to other scenarios.
I interviewed several people from Intuit at the Sleeter Accounting Solutions Conference this week, including (amongst others) Dan Wernikoff, Senior VP.
I'll have an article in my blog on this (http://www.sleeter.com/blog/) next week - I'm transcribing my recordings and clarifying points.
There are a LOT of points here, but to address what you are looking at -
If you are writing an IPP app using V3 for QBO - no problem (and in fact, some good news there).
If you are already published with IPP using V3 and Sync Manager for the Desktop, you will get continued support but don't expect any advancement there (unless you are someone big like American Express).
If you are NOT already published with IPP for the Desktop - the SDK is your option.
And there is a lot more info about this coming out
MINOR EDIT AT A LATER DATE: If you have been working with IPP for the desktop you MIGHT get approved to continue - no guarantees on that (but it seems they might be lenient). But In my opinion you can't expect any significant new features (as in, more data access) moving forward unless you are a significant partner with a contract with them (such as, American Express).
Intuit will not prevent you from going live with your application that you have spent the last 6 months working on. We have a set of guidelines for grandfathering in developers who have invested in using the v2 REST API for QuickBooks Desktop.
feel free to contact me directly if you have more questions.
#Charlie if you could correct your statement regarding if you are NOT published then you need to use the QBXML SDK. That is too generic, we will evaluate each developer on a case by case basis.
regards,
Jarred
My writeup on this subject is available at http://www.sleeter.com/blog/2013/11/quickbooks-software-integration/
Note that Dan Wernikoff, Senior VP at Intuit, has been leaving comments in several of my articles in the blog.
Blair, you have a reasonable concern. However, given the REASONS that they made this change, I would SPECULATE that Intuit won't be pulling the SDK. What isn't clear, at this time, is HOW MUCH support they will give the SDK moving forward.
And, as we have seen for several years now, things can change...

How To Get Started Working with the Google AdWords API?

I'm a student working on a project related to SEO; I need to write an optimization tool, so I'm writing an application using C# and Windows Forms. The main part of the application is for keyword selection, and I want to use the Google AdWords API to obtain a list of keywords.
I downloaded the C# client library, but can't understand how to set up the project: I am getting the error:
"An API exception has occurred. See ApiExecption and InnerException fields for more details".
Maybe I have made a mistake when I edited the App.config file as I haven't changed anything else. Can anyone advise me where I should begin? I would be grateful to hear your ideas.
Unfortunatley, the AdWords API isn't as open as you might think: It's meant for ad agencies managing large accounts, or software vendors who want to build ad management platforms. You need to apply to Google for an API key to gain access; they used to give them out to nearly anyone with an account, and it took about 14 days to process the application. However, Google has got very strict about their terms and conditions over the past 12 months, and to put it simply, you probably won't meet them if you're building an SEO tool; even if you apply to build a full platform, you'll need to wait six to ten weeks for approval as they've got a huge backlog of applications to process at the moment.
As this is just a student project, you should actually be able to get away with just using the AdWords API sandbox, which is open to anyone with a Google account. This won't give you real keywords or stats, but would demonstrate your understanding of the platform.
Another option would be to check out the Ad Intelligence Service of the adCenter API; you'd still need to open an adCenter account (with a $5 activation fee), but you should be able to get an adCenter API key without waiting too long. The stats available from Microsoft won't be as extensive as what Google has to offer, but will still be relevant to the at least the US market. Also, being Microsoft, they've got a good range of C# examples.
You could use the sandbox, but it is good only for testing purposes. You won't get real values for traffic estimation and keyword ideas.
To use the sandbox, what you need is a Google account (your gmail account for instance). To initialize the sandbox,
In your App.config, put email/password/developerToken as your email / your password / youremail++USD (e.g. john.doe#gmail.com++USD)
Run the GetCampaigns.cs code example. It is under v201109/BasicOperations folder in the C# examples project. This will initialize the sandbox.
Run the GetAccountHierarchy.cs code example. It is under v201109/AccountManagement folder. This will give you 5 client emails and their customer ids.
Use one of these customerIds in the ClientCustomerId field of App.config.
Run any other code example.
The video is a bit outdated, due to recent changes in AdWords API, I need to update it.
you can find a very good article series about adwords api there: Google Adwords API
it is not that hard to learn how to use it! I think the API itself is very good documented and there is a good suppo from google.

App Export Compliance using the Dropbox API

This question (or variations of this question) has been asked before, but as Apple's export compliance rules change relatively frequently, and no one seems to ever get a straight answer, I thought I would ask.
I write an iPhone application that uses version 0.2 of the Dropbox API.
I have emailed Apple concerning use of this specific API, and I will be sure to update this question as I learn more and hear back from Apple. In the meantime, if any developer is using the Dropbox API in their iPhone application, did you mark your application as using encryption?
Edit: Upon closer inspection, it looks like the file data is also transferred using SSL. Since their API is using the NSMutableURLRequest class over HTTPS though, I still can't determine whether or not this API "uses encryption." If in the App Store submission page I mark that it does include encryption, Apple then asks if I'm using greater than a 64-bit symmetric encryption key.
If your app uses SSL (HTTPS), then yes it does include encryption. The export compliance rules changed last year though, so you will need an Encryption Registration Number instead of a CCATS number. See this blog post for details.
As it happens I'm working on this right now on a related project.
The Apple position is clarified in the FAQ in iTunesConnect; (my bold)
If your App contains, uses or
accesses standard cryptography for purposes other than those listed in
questions 2-4, you need to submit for
an ERN authorization. Examples of
standard encryption are: AES, SSL,
https.
This authorization requires that you
submit an annual report to two U.S.
Government agencies with information
about your App every January.
It's a pain in the neck, but that is the law if you want to be fully compliant. I'd love to hear that I'm wrong though!
PS. You could always ask for a direct opinion from the Government department concerned here;
http://www.bis.doc.gov/forms/rpdform.html
You can also call the Bureau of Industry and Security help desk at 202-482-0707 or read the web site at http://www.bis.doc.gov/encryption for more information.
Discussing your question with a live person is probably going to be better than filling out the online form and waiting for a response.