document-understanding
latest
false
Document Understanding API guide
- Getting Started
- Examples Using the Document Understanding™ Cloud API v1
- Running API Calls
- Authorize using an External Application and retrieve the available resources
- Use the Discovery APIs
- Use the Digitization APIs
- Use the Delete Document Data service
- Licensing
- Troubleshooting
Authorize using an External Application and retrieve the available resources
Authorize using an External Application and retrieve available resources, including the project ID needed for subsequent Document Understanding API calls.
- Create a new Document UnderstandingTM project and retrieve the
projectId(found within the project's URL).
For this example we are using the predefined project* available in Swagger, identifiable with this projectID: 00000000-0000-0000-0000-000000000000.
Note:
The predefined project is not visible in the Document Understanding UI. It provides programatic access to the available public ML models.
- Create an External Application where Document Understanding is used as a Resource and it includes all the available Application Scopes.
- Initiate a curl call to the Identity Service for obtaining a token.
curl --data \
-urlencode "scope=Du.Digitization" --data \
-urlencode "client_id={app_id}" --data \
-urlencode "client_secret={app_secret}" --data \
-urlencode "grant_type=client_credentials" {AutomationCloudURL}/identity_/connect/token
curl --data \
-urlencode "scope=Du.Digitization" --data \
-urlencode "client_id={app_id}" --data \
-urlencode "client_secret={app_secret}" --data \
-urlencode "grant_type=client_credentials" {AutomationCloudURL}/identity_/connect/token
Note:
The Authorization token has an expiration period. See the following response for the expiration and make sure to renew it before it expires.
{
"access_token": "eyJh**CRaKrg",
"expires_in": 3600,
"token_type": "Bearer",
"scope": "Du.Digitization.Api"
}
{
"access_token": "eyJh**CRaKrg",
"expires_in": 3600,
"token_type": "Bearer",
"scope": "Du.Digitization.Api"
}