Dropbox API

Integrate Dropbox with your product—along with any other
File Storage
 application

Connect your product to all the applications your customers use via Merge's

File Storage

 

Unified API to close more deals, retain customers, and expand to new markets

Your Product
Merge
Your customers' data
Async Passthroughs
Audit Trails
Drives
Field Mappings
Files
Folders
Groups
Scopes
Users

Top integration use cases for Dropbox

Sync Dropbox Data

FAQ on integrating with Dropbox’s API

What are the common endpoint interactions when integrating Dropbox with Merge?

Here’s a look at some of the endpoints you can interact with:

  • Files: Upload, list, and retrieve metadata for files. This is ideal for syncing and organizing documents
  • Folders: Create, navigate, and manage folders to structure data storage
  • Sharing: Manage shared links and permissions for files and folders
  • Users: Access user account information, such as profiles or storage quotas

Learn more about the Dropbox endpoints Merge can interact with.

How often does Merge sync with Dropbox?

Merge supports the following sync frequencies for Dropbox:

  • Daily Sync: Data is synced once every 24 hours
  • Standard Sync: Data is synced every 6 hours
  • High Sync: Data is synced every 3 hours
  • Highest Sync: The most frequent sync, which updates your customers’ Dropbox data every hour

You can also use features like Force Resync (to async data ad hoc) or Automatic Webhooks (to sync data in real-time).

Learn more about Merge’s sync frequencies for Dropbox data.

What other file storage integrations does Merge support?

Once you’ve built to Merge’s File Storage Unified API, you can add integrations with the following file storage applications (in addition to Dropbox):

  • Box
  • Google Drive
  • OneDrive
  • SharePoint

Learn more about the file storage integrations Merge supports.

How does Merge handle syncing custom Dropbox data?

Merge provides several features to help you sync custom data from Dropbox, including:

  • Field Mapping: This allows you to map data fields between Dropbox and your application, ensuring you can access the exact data you need

  • Remote Data: Merge enables you to fetch data from Dropbox dynamically, so you can keep your app up-to-date with the latest information

  • Authenticated Passthrough Requests: You can use this feature to pass requests directly to Dropbox with your customer’s authentication, ensuring secure and customized data access

Learn more about each of these features in Merge’s Docs.

How is your customer's Dropbox data encrypted and where is it stored?

Your customer’s Dropbox data is encrypted both in transit and at rest using industry-standard encryption protocols. 

All data is also transmitted over HTTPS to ensure secure communication between Merge and Dropbox. And the data is stored in secure, compliant cloud environments, adhering to best practices for security and privacy, and can be hosted in regions that meet your organization's specific requirements.

How long does it take developers to set up a Dropbox integration?

Building to Merge’s File Storage Unified API typically takes anywhere from a few hours to a few days.

Once you’ve built this connection, you can easily add integrations with Dropbox and several other file storage systems—all but ensuring that you can integrate at scale, fast.

Are there any days you’ll be closed for the holidays in 2024?
Trusted to power integrations globally
Build Smarter

Make integrations your competitive advantage

More sales, less code, fewer headaches

Focus on your core product

Stop diverting your engineers to yet another integration and let them get back to work.

Give customer success a break

Manage your simplified integration issues in a single pane. No therapist required.

Stop losing sales due to integrations

Launch integrations in days, not quarters. Your sales team will thank you.

APIs Made Simple

The toolkit for all your integration needs

We make integrations painless with accessible API design, dead-simple SDKs, and beautiful documentation that we agonize over.

View docs
Get Employee Data
import merge
from merge.client import Merge
merge_client = Merge(api_key="<YOUR_API_KEY>", account_token="<YOUR_ACCOUNT_TOKEN>")
employee = merge_client.hris.employees.list()
import { MergeClient, Merge } from '@mergeapi/merge-node-client';
const merge = new MergeClient({
  apiKey: 'YOUR_API_KEY',
  accountToken: 'YOUR_ACCOUNT_TOKEN',
});
employee = await merge.hris.employees.list()
ApiClient.instance.authentications.tokenAuth = {
  type: 'bearer',
  accessToken: 'API_KEY',
};
new EmployeesApi().employeesList('ACCOUNT_TOKEN', {}, (data) => {
  console.log(data);
});
import (
  "context"
  "fmt"
  merge "github.com/fern-api/merge-go"
  mergeclient "github.com/fern-api/merge-go/client"
  "github.com/fern-api/merge-go/hris"
)

client := mergeclient.NewClient(
  mergeclient.ClientWithAuthApiKey("<YOUR_API_KEY>"),
  mergeclient.ClientWithHeaderAccountToken("<YOUR_ACCOUNT_TOKEN>"),
)
employee, err := client.Hris().Employees().List(
  context.TODO(),
  &hris.EmployeesRetrieveRequest{
    IncludeRemoteData: merge.Bool(true),
  },
)
if err != nil {
  return err
}
fmt.Printf("Retrieved employee with ID %q\n", *employee.Id)
ApiClient client = Configuration.getDefaultApiClient();
client.setBasePath('https://api.merge.dev/api/ats/v1');
ApiKeyAuth tokenAuth = client.getAuthentication('tokenAuth');
tokenAuth.setApiKey('API_KEY');
CandidatesApi apiInstance = new CandidatesApi(client);
apiInstance.candidatesList('ACCOUNT_TOKEN');
import com.merge.api.MergeApiClient;
import com.merge.api.resources.hris.employees.requests.EmployeesRetrieveRequest;
import com.merge.api.resources.hris.types.Employee;
MergeApiClient mergeClient = MergeApiClient.builder()
    .accountToken("ACCOUNT_TOKEN")
    .apiKey("API_KEY")
    .build();
Employee employee = mergeClient.hris().employees().list(
    EmployeesRetrieveRequest.builder()
        .includeRemoteData(true)
        .build());
{
"id": "0958cbc6-6040-430a-848e-aafacbadf4ae",
"remote_id": "19202938",
"employee_number": "2",
"company": "8d9fd929-436c-4fd4-a48b-0c61f68d6178",
"first_name": "Dirna",
"last_name": "Emanuel",
"display_full_name": "Dirna Emanuel",
"username": "dirnaemanuel",
"groups": [
  "21a54124-397f-494d-985e-3c5b330b8a68"
],
"work_email": "dirna@merge.dev",
"personal_email": "dirnaemanuel@gmail.com",
"mobile_phone_number": "+1234567890",
"employments": [
  "17a54124-287f-494d-965e-3c5b330c9a68"
Meta Endpoint

Programmatically access required schemas

Third-party providers require specific (and often different) fields to write data to their APIs, making your code a mess.

Dynamically fetch required data schemas from Merge’s /meta endpoint to make POST or PATCH requests that just work.

View Docs
Beyond Building

Rely on the best integration observability system

Let our logs, issue detection, and automated alerts save your customer success team time, money, and headaches.

Forget maintenance - let your developers focus on building!

Start for free

How Drata helps thousands streamline their SOC 2 with Merge

Read case study

​​”Working with Merge’s Unified API and beautiful React component took less than a sprint to integrate, test, and release.”

Daniel Marashlian of profile photo
Daniel Marashlian
Co-Founder & CTO

Read more about building and maintaining multiple integrations

A guide to maintaining your product integrations
A guide to maintaining your product integrations
Blog
Blog Posts
10/27/2023
A guide to integrating multiple APIs
A guide to integrating multiple APIs
Blog
Blog Posts
11/13/2023
The top challenges of normalizing multiple API integrations
The top challenges of normalizing multiple API integrations
Blog
Blog Posts
11/20/2023
One Step Ahead

We're the cheat code to your integrations strategy

Revolutionize your integrations strategy for HR, payroll, directory, ATS, project management, ticketing, accounting and CRM platforms.

Start for free or talk to our sales team and learn how Merge makes it easy to add all your integrations in days – not years.
Read more