diff options
Diffstat (limited to 'docs/dyn/documentai_v1beta3.projects.locations.html')
| -rw-r--r-- | docs/dyn/documentai_v1beta3.projects.locations.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/dyn/documentai_v1beta3.projects.locations.html b/docs/dyn/documentai_v1beta3.projects.locations.html index 74116a40c..447f51292 100644 --- a/docs/dyn/documentai_v1beta3.projects.locations.html +++ b/docs/dyn/documentai_v1beta3.projects.locations.html @@ -110,7 +110,7 @@ h1, h2, h3 { <pre>Fetches processor types. Args: - parent: string, Required. The project of processor type to list. The available processor types may depend on the whitelisting on projects. Format: projects/{project}/locations/{location} (required) + parent: string, Required. The project of processor type to list. The available processor types may depend on the allow-listing on projects. Format: `projects/{project}/locations/{location}` (required) x__xgafv: string, V1 error format. Allowed values 1 - v1 error format @@ -121,8 +121,8 @@ Returns: { # Response message for fetch processor types. "processorTypes": [ # The list of processor types. - { # A processor type is responsible for performing a certain document understanding task on a certain type of document. All processor types are created by the documentai service internally. User will only list all available processor types via UI. For different users (projects), the available processor types may be different since we'll expose the access of some types via EAP whitelisting. We make the ProcessorType a resource under location so we have a unified API and keep the possibility that UI will load different available processor types from different regions. But for alpha the behavior is that the user will always get the union of all available processor types among all regions no matter which regionalized endpoint is called, and then we use the 'available_locations' field to show under which regions a processor type is available. For example, users can call either the 'US' or 'EU' endpoint to feach processor types. In the return, we will have an 'invoice parsing' processor with 'available_locations' field only containing 'US'. So the user can try to create an 'invoice parsing' processor under the location 'US'. Such attempt of creating under the location 'EU' will fail. Next ID: 9. - "allowCreation": True or False, # Whether the processor type allows creation. If yes, user can create a processor of this processor type. Otherwise, user needs to request access. + { # A processor type is responsible for performing a certain document understanding task on a certain type of document. + "allowCreation": True or False, # Whether the processor type allows creation. If true, users can create a processor of this processor type. Otherwise, users need to request access. "availableLocations": [ # The locations in which this processor is available. { # The location information about where the processor is available. "locationId": "A String", # The location id, currently must be one of [us, eu]. |