API Credentials
AnsweredCleveland Clinic is trying to access the new API but they are having trouble with access. They are licensed for it and are attempting to follow the instructions in this article. When they are in Momentus Connect Marketplace, the only option in their API header meau is “API Documentation”. They don't have an “API Keys” option. If they click the link links in the API Card, there is no clear point to generate API keys either. See video of the customer's experience.
-
Victor Nogales Junior Seth Halvaksz - Any thoughts on this?
-
I don't know the information here, so will defer to Victor
-
Hello Amy Durbin apologies, I missed this message.
The reason is that there was no Momentus Connect Customer Admin assigned for Cleveland. I confirmed Elizabeth Dang (dange2@ccf.org) as an Enterprise Admin and set her as Customer Admin for Cleveland in Momentus Connect.
Please share this knowledge base article with her explaining Momentus Connect Roles: https://connectsupportcenter.ungerboeck.com/hc/en-us/articles/39315911503511-Users-and-Roles-in-Momentus-Connect
Thanks,
Victor. -
Hi Victor Nogales Junior - That worked for them. Thank you! They have some follow up questions now. See below
Missing endpoints in V2. You'd mentioned the new OData API should include more data than V1, but I'm not seeing that yet. These four endpoints exist in V1 but I can't find them in V2:- Custom_Field_Sets
- Custom_Field_Validation_Tables
- User_Defined_Fields
-
Validation_Entries
They're critical for interpreting the UDF values we pull. For many multiselect fields, the user-defined value only stores a code — the actual value lives in the custom field sets — so without these we can't resolve those codes. Can you confirm whether this data is available in V2, and if so, how to access it? If not, how long will V1 be supported after our crossover to V2?
- Query size limit. The V1 documentation noted a 100,000-record cap per query before it would error out. Is that still in place for V2? It mainly affects the initial load on a few high-volume endpoints, but it'd be useful to know going forward.
-
Hi Amy Durbin ,
Missing endpoints in V2The new Momentus Connect API, assuming you meant V2, combines all existing V1 endpoints (the “Enterprise Standard API” collection in our Momentus API swagger) with a new set of OData endpoints (the “Enterprise OData API” collection). As a Momentus API subscriber, you can access both collections using the same credential. Therefore, all V1 endpoints including the ones you mentioned are available through the “Enterprise Standard API” collection. It’s important to note that the new OData endpoints are still read-only and currently cover 60 endpoints. We’ll be adding more as we go, for example, we launched with 32 endpoints and now have 60.
Query size limit.
The team is investigating this, I'll get back to you as soon as I hear from them.
Thanks,
Victor. -
Hi Victor Nogales Junior - Just checking back on the Query size limit. Any info I can share with the customer?
-
Hi Amy Durbin , apologies, I got the answer earlier in the week and missed to reply to you. See below:
Yes, the 100,000-record limit still applies in Momentus Connect API. Since it uses the same Enterprise backend as V1, this limit remains unchanged.The limit applies per query, not to the total number of records you can retrieve. Larger datasets can be fetched by using pagination:
-
OData:
$topand$skip(for example,$top=10000&$skip=0, then$top=10000&$skip=10000) - Standard API: Use the endpoint’s pagination parameters.
For large initial data loads, pagination is the recommended approach, as very large responses are also more likely to hit gateway timeout limits.
I hope that helps.
Victor. -
OData:
-
This is great Victor Nogales Junior. Thank you so much!
Please sign in to leave a comment.
Comments
8 comments
Date Votes