Q: What Api calls are AutoDigitizing and why such call is not included in Standard API Plans?
In the Wilcom Web API service “AutoDigitizing” means that
- An image (bitmap or vector) is uploaded to the Wilcom Embroidery Engine and a Stitch file (a Wilcom .EMB) or an embroidery machine file (for example .DST) and a TrueView image file (PNG) are requested.
- The AutoDigitizing process itself means that first, the embroidery engine processes the image file and generates an embroidery design (EMB) file from the image on the server.
- THEN, we generate the TrueView image (PNG) or an embroidery machine file (EMB decoded to machine language, for example .DST) from this EMB file.
When invoicing AutoDigitizing calls, user will find two items in this category:
- ArtworkDesign calls
- ArtworkTrueview calls
Each call collects usage information from specific api calls:
Why are such calls not included in standard plans?
AutoDigitizing calls are very resource-intensive and place heavy load on the API Server/Embroidery Engine. These calls can cause magnitudes larger workload than plain api calls, also depend on the size and complexity of the uploaded image. Therefore Wilcom offers this service on a charge-per-call basis.
How to check the usage of AutoDigitizing calls?
Login to your API account and go to your Dashboard
- Select Stats.
- This will show you the overall number of ap calls you website generated.
- You can select the period, for example “last 30 days”.
- To see the specific AutoDigitizing related calls, click on the “Hits” button and the list of api call types opens. If your Account is enabled for AutoDigitizing calls, you will find these in the bottom:
You can select any api call to see the detailed usage of that call (something like the image below) and you can analyze the frequency and distribution of the calls, peak and quiet periods, etc.