Unable to trigger Core Capture Service API endpoint

Mrudhula
Mrudhula Member
edited October 2 in Q&A #1

Hi team, I have been trying to use Core Capture Service but always getting error as

{
  "fault": {
    "detail": {
      "errorcode": "messaging.adaptors.http.flow.InternalServerError"
    },
    "faultstring": "Internal Server Error"
  }
}

I am able to generate the access token but not able to access any services like Session etc..

url which is working for token generation : https://us.api.opentext.com/tenants/6940d09e-0f19-4929-9618-724037d07bc3/oauth2/token

Core capture service urls trying to access which are giving error as stated above :

https://us.api.opentext.com/capture/cp-rest/v2

https://us.api.opentext.com/capture/cp-rest/v2

Kindly guide on how to proceed or if there is any change in url endpoint.

Answers

  • Shahid M
    Shahid M E Community Moderator
    edited July 22 #2

    Hi Mrudhula, your base url for the Capture Service for the US region is correct. Can you try one of the APIs, such as getting a list of document types as shown in the screenshot.

    And just in case, here's a screenshot of generating the OAuth2 token within the same API.

    Let us know how it goes.

  • Roger K
    Roger K E Community Moderator
    edited July 23 #3

    For the benefit of those who may be trying to use capture service, the servers list in the API documentation for Capture is out of date, and has not been updated to take account of our new regions.

    If you are using Capture via the developer experience and chose a region for your trial, then the server url will be as follows, with the region code being us, ca or au depending upon the region you chose for your trial:
    https://<region>.api.opentext.com/capture/cp-rest/v2/

    If your account has existed for some time and when you created your account you were not given a choice of region for it, then url to be used will be: https://na-1-dev.api.opentext.com/capture/cp-rest/v2/

    For the purposes of the developer experience trials - you can ignore the remaining urls in the servers list of the API documentation as these are for various production deployment options.

    @Mrudhula - please can you try again? There was an issue with the Capture service in the us region around the time you reported this issue, which has now been addressed. I

  • Hi Shahid/Roger,

    Thank you for the response. I have tried now and able to access.

  • Karen Weir
    Karen Weir E Community Administrator

    Thanks Roger

    The servers list in the Capture API have been updated.

    We are still working to resolve the 'authenticate' function that allows for selecting the region.