OData API Help
Cleveland Clinic is trying to utilize the new OData API. They have been licensed for it but they are running into some roadblocks and aren't sure how to proceed. Do we have any documentation on the following questions from the customer?
- Our developer was trying to take a look at the new API, but said he needed API keys to access the data to be able to write test queries. Do I need to initiate the API Request on Momentus Connect to get that access, or how can he get the API key to view the data? Or are we going about this wrong? He is looking into what tables may need to be pulled.
- On Momentus Connect, I see two tenants, but they seem to have the same code. Since I am new to this side of Momentus, what does this mean?

-
I'm going to let someone who knows what they're talking about address the tenant and activation questions, but once that's all sorted, they'll be able to create API credentials in Connect. There's an article for that here: https://connectsupportcenter.ungerboeck.com/hc/en-us/articles/38776028988439-Add-and-Manage-API-Credentials
-
Thanks for the quick response Linda! I did send them the Momentus Connect support center resources about the API, including this one. Will wait to hear about the tenant and activation!
-
It looks like we don't have an API-specific forum. Do we need one Linda?
Tagging Victor Nogales Junior on the question.
-
Hi Amy Durbin , in your example, the two tenants share the same SiteId because they belong to different organisations within the same Enterprise Site. This is because apps can be configured differently based on the organisation.
Thanks, Victor.
-
Hi Victor Nogales Junior - I'm not sure I follow. Will they select whatever organization they want to work with the API in and then go back and forth as needed? Or do they need to select a default Org? Cleveland Clinic has 15 orgs within their database so I may need a little more clarity for them.
-
I have added an Enterprise APIs and an Elite API forum. These are on the Enterprise and Elite pages, so Victor Nogales Junior your team will need to go to those pages to subscribe.
-
Hello Amy Durbin ,
Momentus Connect was designed around the concept of separating configurations by organization within an Enterprise environment. As a result, we create a separate Tenant for each organization.
That is why you may see multiple tenants with the same SiteId — they represent different organizations under the same Enterprise Site ID.
The reason for this design is that each organization can have its own configuration and setup. For example, with the Outlook integration, different organizations may require different space mappings.
Momentus APIs are an exception to this model because Enterprise does not use separate API credentials per organization. Regardless of which organization the credentials were created under, the API can return data from any organization. It is the responsibility of the calling application to specify which organization’s data should be returned. If you review the API endpoints, you’ll notice they all require an organization identifier as part of the request.
We do have plans on our roadmap to make the Momentus API visible across all organizations to reduce this confusion. In the meantime, please advise the customer that credentials created under one Tenant (organization) can still be used to retrieve data from any organization they need access to.
Thanks,
Victor -
Thanks for clarifying Victor Nogales Junior This is super helpful info. I'll pass along to the customer.
Please sign in to leave a comment.
Comments
8 comments
Date Votes