What authentication does the Detect Language API use?

Detect Language uses bearer token authentication. The token is sent in the Authorization header. Through Jentic, the bearer token is stored encrypted in the credential vault and injected at call time.

Can I run batch language detection with the Detect Language API?

Yes - POST /detect/batch accepts an array of texts and returns one detection per item, which is significantly more efficient than calling /detect in a loop for large content sets.

How many languages does the Detect Language API support?

The API detects 216 languages. Call GET /languages for the full list with ISO codes; this list is the canonical reference for what the /detect endpoint can return.

What are the rate limits for the Detect Language API?

Limits are tied to the account's daily detection quota rather than per-second rate limits. Call GET /user/status to read remaining quota and set up alerts before exhaustion.

How do I detect the language of an inbound message through Jentic?

Search Jentic for 'detect text language', load the /detect operation, and execute it with the message text. Jentic injects your bearer token at execution and returns the language code with confidence.

Can I limit what my agent is allowed to do with the Detect Language API?

Yes. Because you run Jentic One yourself, your own rules decide which Detect Language operations and credentials the agent may use, and it can only call the ones you import. Detect Language takes the text to identify in the request body rather than a scoped URL path, so you can grant just single detection with POST /detect, or add batch detection with POST /detect/batch, without exposing anything else. Account status from GET /user/status and the supported-language list from GET /languages are available to the agent only if you add those operations.