Configure the Client
Reference documentation on preparing and configuring the Mindee client.
Requirements
Before proceeding you'll need to have one of the official Mindee client libraries installed.
You'll also need to use one of your Integration Overview and one or several Models configured.
Overview
Before sending any files to the Mindee servers for processing, you'll need to initialize your client and set inference options.
These settings will determine how your files are sent, including any extra options, and how you want to process the result.
Initialize the Mindee Client
This should be the first step in your code. It will determine which organization is used to make the calls.
You should reuse the same client instance for all calls of the same organization.
The client instance is thread-safe where applicable.
First import the needed classes:
from mindee import ClientV2, InferenceParametersFor the API key, you can pass it directly to the client. This is useful for quick testing.
api_key = "MY_API_KEY"
mindee_client = ClientV2(api_key)Instead of passing the key directly, you can also set the following environment variable:
MINDEE_V2_API_KEY
This is recommended for production use.
In this way there is no need to pass the api_key when initializing the client.
mindee_client = ClientV2()First import the needed classes. We recommend using TypeScript.
const mindee = require("mindee");
// for TS or modules:
// import * as mindee from "mindee";For the API key, you can pass it directly to the client. This is useful for quick testing.
const apiKey = "MY_API_KEY";
const mindeeClient = new mindee.ClientV2({ apiKey: apiKey });Instead of passing the key directly, you can also set the following environment variable:
MINDEE_V2_API_KEY
This is recommended for production use.
In this way there is no need to pass the apiKey argument when initializing the client.
const mindeeClient = new mindee.ClientV2();First import the needed classes:
For the API key, you can pass it directly to the client. This is useful for quick testing.
Instead of passing the key directly, you can also set the following environment variable:
MINDEE_V2_API_KEY
This is recommended for production use.
In this way there is no need to pass the $apiKey when initializing the client.
First import the Mindee package:
For the API key, you can pass it directly to the client. This is useful for quick testing.
Instead of passing the key directly, you can also set the following environment variable:
MINDEE_V2_API_KEY
This is recommended for production use.
In this way there is no need to pass the api_key when initializing the client.
First import the needed classes:
For the API key, you can pass it directly to the client. This is useful for quick testing.
Instead of passing the key directly, you can also set the following environment variable:
MINDEE_V2_API_KEY
This is recommended for production use.
In this way there is no need to pass the apiKey argument when initializing the client.
First add the required namespaces.
For the API key, you can pass it directly to the client. This is useful for quick testing.
Instead of passing the key directly, you can also set the following environment variable:
MindeeV2__ApiKey
This is recommended for production use.
In this way there is no need to pass the apiKey argument when initializing the client.
Set Inference Parameters
Inference parameters control:
which model to use
server-side processing options
how the results will be returned to you
Use an Alias
You can set an alias for linking the sent file to your own system.
For example, you could use an internal PO number, or your database ID.
Aliases are not unique in our database, you can use the same alias multiple times.
Only the model_id is required.
Only the modelId is required.
Only the modelId is required.
Only the model_id is required.
Only the modelId is required.
Only the modelId is required.
Optional Features Configuration
Enable or disable Optional Features.
The default activation states for Optional Features are set on the platform. Any values set here will override the defaults.
Leave empty or null to use the default platform values.
For example: if the Polygon feature is enabled on the platform, and polygon is explicitly set to false in the parameters ⇒ the Polygon feature will not be enabled for the API call.
Only the model_id is required.
Only the modelId is required.
Only the modelId is required.
Only the model_id is required.
Only the modelId is required.
Only the modelId is required.
Polling Configuration
The client library will POST the request for you, and then automatically poll the API.
When polling you really only need to set the model_id .
You can also set the various polling parameters. However, we do not recommend setting this option unless you are encountering timeout problems.
When polling you really only need to set the modelId .
You can also set the various polling parameters. However, we do not recommend setting this option unless you are encountering timeout problems.
When polling you really only need to set the modelId .
You can also set the various polling parameters. However, we do not recommend setting this option unless you are encountering timeout problems.
When polling you really only need to set the model_id .
You can also set the various polling parameters. However, we do not recommend setting this option unless you are encountering timeout problems.
When polling you really only need to set the modelId .
You can also set the various polling parameters. However, we do not recommend setting this option unless you are encountering timeout problems.
When polling you really only need to set the modelId .
You can also set the various polling parameters. However, we do not recommend setting this option unless you are encountering timeout problems.
Webhook Configuration
The client library will POST the request to your Web server, as configured by your webhook endpoint.
For more information on webhooks, take a look at the Webhook Results page.
When using a webhook, you'll need to set the model ID and the webhook ID(s) to use.
You can specify any number of webhook endpoint IDs, each will be sent the payload.
Next Steps
Now that everything is ready to, it's time to send your files to the Mindee servers.
If you're sending a local file, head on over to the Load and Adjust a File section for details on the next step.
If you're sending an URL, head on over to the Send a File or URL section.
Last updated
Was this helpful?

