I'm trying to automate export of a published Smartsheet. I've seen various API examples, but all of them need {sheetId}. Unfortunately I just have the URL of the published sheet, and no access to the base sheet.
Is there a way to do an export to excel programmatically on a published Smartsheet?
Are you the owner of the sheet?
In addition to the sheet id, you will need an access token that has permission to access the sheet in order to programmatically extract the data.
The only alternative would be scraping the data, which would be a painful endeavor.
Related
With PHP, I create a smartsheet from excel file with smartsheet API. Everything is working fine so far. But I also want to give right access to the new smartsheet to a specific user to allow him to open it from a browser.
The user already has a smartsheet account.
Is there a smartsheet endpoint that allows this to be done?
Thank you
The operation you're looking for is Share Sheet.
The following example request grants the Smartsheet user who's registered with email address jane.doe#test.com EDITOR (write) access to the sheet that's specified by sheetId in the request URL.
POST /sheets/{sheetId}/shares
[
{
"email": "jane.doe#test.com",
"accessLevel": "EDITOR"
}
]
A couple of notes:
By default, the Share Sheet operation won't send an email to the user to notify them that they've been granted access to the sheet. If you want it to send them an email, you'll need to specify the query string parameter/value sendEmail=true on the request URL, and specify the message and subject properties in the body of the request. See Share Sheet in the API docs for details about this.
If you want the user to be able to share the sheet with others, you'll want to specify EDITOR_SHARE as the access level (instead of EDITOR). See Access Levels in the API docs for details about the various permissions.
Is it possible to add custom attachment type that is displayed in the dropdown menu and provides custom attachment creation process?
I've quickly looked over API Documentation and I found some methods with which I can download/upload attachments through API calls.
But I didn't found any info how I could integrate my custom attachment process into regular smartsheet workflow.
If I understand correctly, you're looking for a way to extend the list of options that the Smartsheet user interface (UI) shows for uploading an attachment (by adding your own custom option to that list). Is that correct?
If that's what you're looking to do, then unfortunately that's not possible. You can't use the API to change UI components of the Smartsheet application itself.
My company keeps individual employee schedules. Each employee manages their own schedule. Admin,supervisors and project manager have to go to each sheet and look for the information.
I need to create a system that allows someone to select a date range and skill set then produce a sheet with the information that matches the criteria. I have installed the Python API and worked through a few tutorials.
Now I need to know how to make command buttons, date pickers . . .
A quick read of my search results indicates that this is not part of the Smartsheet API!
Is there a way to do this through the SmartSheet API? Or how would you approach this?
The Smartsheet API enables you to programmatically access data in Smartsheet (i.e., create, read, update, delete data in Smartsheet). This is true for all APIs -- they simply provide a means for you to programmatically access data. You'll need to build the web app's user interface (UI) yourself by using HTML, CSS, JavaScript, etc.
Alternatively -- instead of building a custom web application like you've described -- I'd suggest that you look into the possibility of creating Smartsheet Reports that can provide the data you've described. You can create Smartsheet Reports via the Smartsheet UI -- so you wouldn't need to do any programming at all.
I would like to know if there is a default feature for importing products export files in json/xml/csv format and if this can be called daily with a cron or something automatically.
Thanks,
Tibi
You are free to create a private App that has scope permissions to write_products, write_inventory and read_locations. With that, you can establish a script that can parse your json/xml/csv and update inventory. That script can be scheduled to run as often as you need. Shopify is an ideal platform for the use of scripting to accomplish many manual tasks.
I agree with David. You need to create a custom App in your store and submit your data to a script(you can use PHP) triggered by CRON hosted on a server which will create a record using Product API.
Step 1: Go to Apps tab in admin section of your store. Scroll down and click on Manage private apps, create an App here to generate API keys and password.
Step 2: Create and host(on a secured server) a script that will use API keys generated in previous step to create new product record using https://help.shopify.com/en/api/reference/products/product#create
Step 3: Fetch your data in any format and send this data in JSON format to your Shopify store using API. A new product record will be created in your store.
Note: You can test this API by using credential created in Step 1 on Postmen tool you can refer https://help.shopify.com/en/api/reference/products/product#create. You will have to hit Example URL generated in Private app from Step 1.
How can I view a raw text file on GitHub?
I created an unlisted REPO and inside the repo is a text file.
When I view it in raw format I get exactly what I want. And if I use C# to Download the text of that page, I get what I want.
My only concern is that the link to the github raw file is
https://raw.githubusercontent.com/USERNAME/STUFF/master/version.txt?token=THETOKEN
Does the THETOKEN part ever change? Like can I use this link for the rest of my life to access that raw text file? Or does the link change?
The token part is an auth token so it will work as long as that set of credentials is valid (until you revoke it). However, you should still manage that token as a secret.
If you plan to share this C# program with others you should not share your token with them, since this will give them access to other parts of your GitHub account.
If you want to share this file publicly you should publish it to a public CDN or another service that provides access control. For example you can use Amazon S3 with signed URLs for a few cents a month.