Ink Recognizer Client
The service is used to perform ink layout and recognition of written words and shapes. Ink strokes passed to the service are recognized and organized into…
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
The service is used to perform ink layout and recognition of written words and shapes. Ink strokes passed to the service are recognized and organized into recognition results in the response
Endpoints 1
InkRecognizer
- PUTInkRecognizer_Recognize
/recognizeInk Recognition operation is used to perform ink layout and recognition of written words and shapes. It allows passing the ink strokes to the service to get…
API details
- Base URL
https://azure.local- Authentication
- An API key in the Ocp-Apim-Subscription-Key header
- Operations
- 1 operation on 1 pathPUT 1
- Main resources
- InkRecognizer 1
- Response formats
application/json- Description format
- Swagger 2.0, API version
1.0 - Links
- OpenAPI document
- Listed from
- APIs.guru OpenAPI Directory (CC0-1.0)
Source updated
How to test the Ink Recognizer Client in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Ink Recognizer Client collection, without the publisher's secrets.
- Add your credentialsThis API uses an API key in the Ocp-Apim-Subscription-Key header. Add yours in the collection's variables or an environment; the requests already reference it.
- Send a requestPick an endpoint, for example “InkRecognizer_Recognize” (PUT /recognize), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Ink Recognizer Client?
The service is used to perform ink layout and recognition of written words and shapes. Ink strokes passed to the service are recognized and organized into… It is listed under Developer tools and has 1 endpoint.
Who publishes the Ink Recognizer Client?
It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Ink Recognizer Client?
Requests go to https://azure.local. Endpoint paths are added to this base URL.
How do I authenticate with the Ink Recognizer Client?
With an API key in the Ocp-Apim-Subscription-Key header.
How many endpoints does the Ink Recognizer Client have?
1 operation on 1 path (1 PUT). The largest groups are InkRecognizer.
Is forking the Ink Recognizer Client free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.