If I have a Core Content subscription, can I use the OT2 Core APIs directly?
Hi OT2 Team,
I have access to a trial of OpenText Core Content (SaaS App) This is working fine and we can access the web interface, add content etc. As part of evaluating the Core Content platform, we need to confirm whether we can interact/add content using available APIs.
Reading Content Storage Services and Content Metadata Services which allow developers to upload files, manage types, object attributes and permissions. Core Content then adds APIs that allow Core Content customers to extend and integrate their organization’s tenant via this APIs."
, this states that "The underpinnings to Core Content are theThis leads me to believe that I should be able to use these APIs directly, rather than only interacting with content directly via the Core Content UI/App.
Thing is, I have been unable to get this to work using the Postman project from
It would seem that I do not have rights/privileges to the APIs directly - as I cannot seem to obtain a valid OAuth token, despite being able to signin to Core Content!
So my question is - if a customer has only subscribed to the SaaS Core Content (App), does this entitle them to use the Core APIs directly, associated with the same subscription/tenancy that the Core Content app resides under?
Regards,
David
Answers
-
Hi @David Henshaw , I have shared your inquiry with the team
0 -
Hi David,
I will need to look up your trial subscription configuration to determine how it was set up; if it includes API access or not. For starters, could you please share the URL you use to access Core Content trial? That will give me the data center and subscription name which will help me.
0 -
Hi Karen - I believe trial has been setup in EU region. URL I use to access SaaS Core Content App is https://corecontent.ot2.opentext.eu/subscriptions/fastman-corecontent?userEmail=ZGF2aWQuaGVuc2hhd0BmYXN0bWFuLmNvbQ
Can I pick up on your comment "..if it includes API access or not". Does this imply that customers who sign up for Core Content (the app) do not automatically have entitlement to use the Core Content APIs directly? Or that they need to have an additional API plan?
We're looking to build solutions above Core Content (the app) - i.e. we need to be able to ingest/export/modify content stored in Core Content, using the APIs, such that those events then present throught he Core Content app UI. If a separate API plan is required for that kind of scenario, ouch!
0 -
Thank you David,
I will verify with Product Management about the inclusion of APIs. I will also connect you directly to the team so that we can explore your initiatives in more detail.
0 -
Thank you for confirming via email that you have connected with Alex from our PS team. If you need anything further, please let me know David.
0 -
Hi Karen and David,
I'm going through the same situation as David and I'd like to know if any configuration must be done to work with the Core Content APIs.
I would appreciate if you could help me with this problem.
0 -
Thanks @Jaime Galvis , I will get you in touch with our team to review your subscription and provide any information needed.
1 -
For access to public APIs, additional steps need to be performed. These requirements are outlined in this link:
In short, you need:
- have an organization created and proper developer plan added via fulfillment.
- Create an extension app for your Core Content subscription.
During the creation process of the extension app, you will be prompted to download your unique client ID and client secret pair. This client id/secret pair will be needed for all future authentications with public API gateway.
0
Categories
- All Categories
- 118 Developer Announcements
- 52 Articles
- 150 General Questions
- 137 Services
- 56 OpenText Hackathon
- 35 Developer Tools
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 912 Cloud Fax and Notifications
- 82 Digital Asset Management
- 9.3K Documentum
- 30 eDOCS
- 175 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 6 XM Fax