Client Data Export - Domo API?

welyk1974

We currently import a Dataset of Daily Sales Transactions that combine data for 2 clients of ours.  We are using Magic ETL to strip out and create a new dataset for each client. We are looking into options (Must be automated and not manual) for of allowing the client to access their dataset for their internal reporting.   In an ideal world we could automate the export of this file to and SFTP server, or a BOX account..etc.  I have looked into the Domo API but from the looks of it if we set them up to access the API as a client, they would have exposure to all of our datasets(Not just their own) which would put us at risk from a security standpoint. Is there a way to lock down the dataset security and use the API or would you suggest an alternative option?  THX!!!

marcam

You are correct. You do not want to give the customer access to the Domo API for your account.

 

The best way to ensure data security is to use the API yourself to pull the data already filtered or filter it as you're pulling it. Then load that data to an SFTP server. Finally, give your customer access to the SFTP server to access the data.

 

This is a two-step process. While the Domo API offers generous guidance and documentation, you will also need to consult the API documentation for the SFTP (or Box) to automate the second portion of this process.

marcam

You are correct. You do not want to give the customer access to the Domo API for your account.

 

The best way to ensure data security is to use the API yourself to pull the data already filtered or filter it as you're pulling it. Then load that data to an SFTP server. Finally, give your customer access to the SFTP server to access the data.

 

This is a two-step process. While the Domo API offers generous guidance and documentation, you will also need to consult the API documentation for the SFTP (or Box) to automate the second portion of this process.

anafziger

Are limited API keys on the roadmap at any point? We deal with HIPAA compliance and not being able to limit access by Key severely restricts our ability to automate securely.

We can't have an API key that can access PHI floating out in an AWS Lambda for example.

 

Thanks,

user07200

is there any updates to this? 

cadellfalconer

---

@welyk1974 wrote:

We currently import a Dataset of Daily Sales Transactions that combine data for 2 clients of ours.  We are using Magic ETL to strip out and create a new dataset for each client. We are looking into options (Must be automated and not manual) for of allowing the client to access their dataset for their internal reporting.   In an ideal world we could automate the export of this file to and SFTP server, or a BOX account..etc.  I have looked into the Domo API but from the looks of it if we set them up to access the API as a client, they would have exposure to all of our datasets(Not just their own) which would put us at risk from a security standpoint. Is there a way to lock down the dataset security and use the API or would you suggest an alternative option?  THX!!!

---

You may want to consider talking to your Customer Success Manager about Domo's Integration Cloud or "Writeback Connectors" which should help you automate this process and drop files out to other locations.
Here is some information in the mean time: https://www.domo.com/product/bidirectional-data-exchange