Your API key has constraints that determine the capabilities available to you based on the contract you have in place.
These restrictions typically pertain to computational time usage limits per conversion or maximum input file size, among others.
These constraints can be further customized using the limits object within the job's JSON request.
The following parameters are available for sending the request:
||Set the maximum credit that can be spent by the job.
||Set the maximum number of inputs accepted by the job.
||Set the maximum processing time, in seconds, for the job.
||Set the maximum file size for the job inputs.
||Set how many times a converted file can be downloaded.
It is important to note that the fail_on_conversion_error boolean value may impact the functionality of the limits.
The example shows a job that is being sent with a single image as the common input and three separate targets,
allowing you to convert the image into different formats using just one job.
If you wish to limit the number of credits used, you can set the max_credit limit.
However, the behavior may vary based on the value of fail_on_conversion_error, as described in the table below:
||Conversion is done and 3 credits are deducted from your account.
||The time spent is more than the allowed one.
Conversion fails and no credits are deducted from your account.
||The time spent is more than the allowed one, but you choose to not fail the conversion.
Conversion partly succeeds and the conversions' outputs that first reached the max allowed of 2 spent credits are present.
Just 2 credits are deducted from your account.