Glue API First Step FAQ

Here are some of questions that we receive when giving an access to Glue ADN sandbox for the first time:

  1. Glue login problem
  2. Downloading API key and secret
  3. Sign-in using API
  4. Trouble with display component

The most frequently asked by the first time Glue API user is about login. Although it’s not exactly an API question by itself, let me start off with this topic.

Continue reading “Glue API First Step FAQ”


Tools for Testing REST API

There are a couple of tools that I found are very useful when testing Glue and Field REST API calls. As I think it’s not just for me and anybody who is using REST API would benefit, I’m going to give a quick summary here. The ones that I’m currently using actively are:

Continue reading “Tools for Testing REST API”

Rings, Earrings and 3D Printing – Girls Technology Day

Several women and a man from Autodesk Manchester and Waltham offices were at a local event called Girls Technology Day today. The event was sponsored by the State of New Hampshire, Department of Education and held at Manchester Community College. The goal of the event was to promote girls in engineering and get high school freshmen and sophomore female students interested in various engineering fields and applications. 250 girls from 25 high schools were invited to attend.

Autodesk Manchester office was first contacted back in December. Since then, a group of women who volunteered to help got together occasionally and brainstormed/discussed what we could do to help the event. At the end, we decided to do two types of hands-on classes as well as taking part in the vendor space.

Continue reading “Rings, Earrings and 3D Printing – Girls Technology Day”

AEC Hackathon 2.1 Chicago

As I was writing in my earlier post, there was AEC Hackathon in Chicago over the weekend of March 6~8. This time, no snow, and I could make it (although it was still freezing cold when I arrived). It was a different story for Jaime who was flying from New York; New York was hit by yet another snow storm. After his flight was cancelled three times and taking detour, he ended up spending more than 24 hours to fly from NY to Chicago. Usually those things happen to me. (My manager always tells me that he will never ever travel with me.) Feels like Jaime kindly took the Jinx from me. Any way, we both arrived to the opening of the event on time. Two colleagues (one being soon-to-be an official colleague) were there as well: Colin McCrone from Computational Design team and Mohammad Rahmani Asl who just finished his Ph.D., and will be starting as a member of Energy Performance Analysis team in May.

Continue reading “AEC Hackathon 2.1 Chicago”

Lab4 View and Data API Web Intro JS

(This is a continuation from the previous post: Lab3 “View and Data API Web Intro”)

Now that we have a model uploaded to the A360 storage, the final piece of API functionality that we want to add to our Intro Labs app is an ability to view the uploaded model. To do this, View and Data API provides a client side JavaScript API.

If you look at the Quick Start guide, you can see there are a little bit of coding required for this portion. With very little explanation of what each line of code does (or at least I haven’t seen any), however, it may not be so obvious what the code is doing. In this post, I will try to take a look in more detail. Hopefully it will help understand if you are new to the API.

Continue reading “Lab4 View and Data API Web Intro JS”

Lab3 View and Data API Web Intro

(This is a continuation from the previous post: Lab2 “View and Data API Intro”)

In the previous lab, we wrote a desktop client application that can upload a file to A360 storage. Those functions we wrote to make REST calls can be easily included in your authoring tools, such as Revit and AutoCAD. Next, we write a simple ASP.NET web application. For now, we keep the basic functionality same as Lab2 (i.e., authenticate, create a bucket, upload a file, and register) as a way to compare differences. Later on in the Lab4, we will add JavaScript layer to embed a viewer.

The good news is that we have written the functions to make the View and Data web services REST calls in a way that we can simply reuse them. In the sample project, we put the common View and Data REST calls under ViewData folder. You can simply copy the folder to your web application if you have followed lab1 and 2.

Continue reading “Lab3 View and Data API Web Intro”

Lab2 View and Data API Intro

(This is a continuation from the previous post: Lab1 “Hello View and Data World”)

In Lab1, we learned how to obtain an access token and got familiarized ourselves with the basics of REST call. Let’s move on, and try to upload a model and to make it ready for viewing.

To achieve this, we use the following services:

  • Authentication/v1/authenticate (same as in the Lab 1)
  • oss/v1/buckets
  • oss/v1/buckets/{bucket key}/objects/{object key}
  • viewingservice/v1/register

where oss stands for Object Storage Service.

Continue reading “Lab2 View and Data API Intro”

Lab1 Hello View and Data World

(This is a continuation from the previous post: Autodesk View and Data API Intro Overview)

In this lab, we learn the first step into the View and Data world and the basic of REST API call. This is a simple Windows Forms application written in C#. The View and Data services we use in this lab is authentication/authenticate, which is a call to obtain an authentication token required for subsequent calls.

To make REST calls, we use a library called RestSharp. We chose this as the syntax of RestSharp nicely reflects the semantics of REST call and makes it easy to read the code even if you aren’t writing in C#. Please refer to this post about how to include RestSharp library to your project.

Continue reading “Lab1 Hello View and Data World”