What authentication does the SmartDialog API use?

SmartDialog uses HTTP Bearer token authentication on the Authorization header. Through Jentic, the token is held encrypted in the vault and supplied to the call at runtime, so the agent context never holds the raw secret.

Can I create dialog flows programmatically with the SmartDialog API?

Yes. POST /dialogs accepts a dialog definition body and creates a new flow. GET /dialogs/{id} returns the resulting configuration so you can verify the create succeeded.

What are the rate limits for the SmartDialog API?

Arena does not publish hard rate limits in the public spec. In practice, the platform is meant for management traffic rather than message-per-second loads - keep dialog list polling to once per minute or less and rely on conversation listings for batch reads.

How do I list all dialogs through Jentic?

Run pip install jentic, then search Jentic with 'list SmartDialog dialogs', load the returned schema for GET /dialogs, and execute. The response is a list of dialog flow definitions you can iterate over.

Can I read the conversations a dialog has handled?

Yes. GET /conversations returns conversation records produced by dialogs, which you can filter to a specific dialog via the appropriate query parameter described in the spec.

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

Yes. You run Jentic One yourself, so your own rules decide which SmartDialog operations the agent may call and which bearer token it uses. Because the dialog id sits in the URL path at /dialogs/{id}, you can pin the agent to fetching and updating specific dialogs while excluding creation via POST /dialogs and transcript reads via GET /conversations. Only the operations you allow are ever available to the agent.