Since 3D Repo contains multiple API endpoints that retrieve various data from our servers, it's crucial to know how these datasets correspond to each other. For example, if you convert the response payload into a table, you'll find that each row contains a unique ID. Various datasets can be linked together using unique IDs. 💡

As a user, you can establish these connections manually, or if you're using Power BI, it can identify them automatically. Here is an example of how unique IDs will link your tables together. 👇

Common API requests and their response IDs

If you're not familiar with our APIs and how they work, visit our Understand APIs help article. For those of you who are looking for answers, let's dive right into it. When you connect various applications with 3D Repo or want to connect multiple API responses from our servers, here are the most common API requests and the unique IDs they contain:

3D Repo APIs ID relationship diagram

Now, that all may seem a little complicated, given that each API call returns you a unique ID under a different header. Our servers will return you information based on your requests, such as a list of issues, risks or model data. Even though not all of them will have similar IDs, you can still link them all together. Here is a visual graph to show you how you can create a relationship between different API requests. 🧐

Did this answer your question?