Thrust Services
Build new extensions and automation to OpenText Core apps, or develop new innovative apps that delight your customers.
-
New! Forms service
recently posted to the Announcements channel: cross-posting here to reach all of our developer community members. New service added to OpenText Thrust Services bundle Forms is a robust and flexible framework that enables the creation of modern, dynamic forms and user interfaces (UI) through a WYSIWYG Designer. It allows…
-
New Developer site structure
OpenText Cloud Platform (OCP) powers the OpenText Core family of multi-tenant SaaS applications and Thrust Services. Cloud Platform We created a new section on the site that documents all platform concepts such as our approach to Organization/Region/Tenancy, Authentication models, Admin Center functionality, Guides, and…
-
Integration of css / cms api's with workfront which required specific endpoints
We are working on integrating Workfront with OpenText using CSS and CMS APIs to store files or images on OpenText and access them from the Workfront side. However, we are encountering an issue where Workfront appends certain fixed endpoints to the base URLs, such as /files (which we have for the CSS API), /metadata,…
-
Get public url of signed document
This discussion was created from comments split from: NEW! Core Signature Service.
-
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…
-
Core Content missing Storage API URL
Hi , what is the Content Storage Service API URL for the customer. We know it for the developers, but we cannot find it for our Core content subscription.
-
Multiple references (soft/symbolic links?) to a single document, each with own metadata.
Hello all, For all 'normal' documents uploaded to core content we currently store a customer reference in the custom properties attribute of the metadata for each document, along with some other data like the 'read date'. The first time a customer downloads/reads a document, we set this 'read date'. This is all handled…
-
Postman to https://corecontent-ot2devx.devxprod.ot2.opentext.com/subscriptions connection
I am new to opentext and i wanted to understand how can i integrate postman to content server which is on web and looks like…
-
Documentation for ACL permissions in CMS
I could not find any documentation about the different ACL permissions in Content Metadata Service (e.g., the difference between 'write' and 'write_content'). Is the full list documented in detail anywhere?
-
What is the size limit for content upload using the Content Storage Service Version 2 API?
I am using Content Storage Service v2 APIs to upload files to OpenText, and I want to know the maximum upload size limit for content. And also is there any limitation on how many api calls we can make per sec
-
API authentication questions
This discussion was created from comments split from: OpenText APIs Quick Start Guide.
-
getting "Failed to find configuration. Category: ImageProcessing, Configuration name: BW."
using below code to make call capture service but getting error err: "Failed to find configuration. Category: ImageProcessing, Configuration name: BW." http://function handleEnhance() { if (!capturedFileId) { console.error("No file uploaded"); return; } console.log("Enhancing Image"); const enhanceUrl =…
-
Error while creating namespace in Content metadata service
Hi team, I am trying to create namespace in cms using postman as well as swagger ui in portal, but getting error as below { "path": "https://us.api.opentext.com/cms/namespaces", "title": "Internal Server Error", "status": 500, "details": "Current user could not be found; nested exception is…
-
Review document complete url
This discussion was created from comments split from: NEW! Core Signature Service.
-
Calling document api to create document from content
This discussion was created from comments split from: NEW! Core Signature Service.
-
401 Unauthorized error while making request to API using Python. It indicates access token "invalid"
I’m encountering a 401 Unauthorized error while trying to make a request to API. The error message indicates that the access token I'm using is "invalid." Here’s what I’ve tried so far: Verified the Access Token: Double-checked for any typographical errors in the token. Confirmed that the token is in the correct format…
-
Account Lockout Notice
My account has been locked out , the email notification says "This is an administrative notification for tenant '**********************0ac2'. The account for '*****************' has been locked out for the configured duration due to excessive failed authentication attempts" . I need information on how to unlock it ASAP ??…
-
getting auth errorError: Unauthorized, using my login email and password as username and password.
using my login email and password as username and password. but showing error, also follow other steps, and other informations are correctly.
-
Getting error while trying to generate access token for a particular tenant.
-
Available authorizations Server
I have made my organization on us server but the only available server available are na servers and every time i try to autherize api i get authentication error, is it due to different servers or i am entering my creds wrong?