Can I limit what my agent is allowed to do with the Generali Care Hub Backoffice API?

Yes. Write a rule that allows only the operations the agent needs, such as creating and reading service requests, so it can handle intake without editing providers, contracts, or regions. Destructive operations like deleting a service provider or a contract are not included unless you add them, and every call the agent makes is logged.

What authentication does the Generali Care Hub Backoffice API use?

The Generali Care Hub Backoffice API authenticates with a bearer token (a JSON Web Token) sent in the Authorization header, per its OpenAPI spec, and it also exposes local login operations that issue that token. Through Jentic the token is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs.

Can I register a service provider and assign it to a region with this API?

Yes. You register the service provider, add its drivers and driver vehicles, and then create a service-provider-region record to assign the provider to the regions it covers. This keeps the dispatch roster and its coverage in one place for routing requests.

What are the rate limits for the Generali Care Hub Backoffice API?

The OpenAPI spec does not specify rate limits for the Generali Care Hub Backoffice API. For current limits and environment details, check the documentation provided with your Generali Care Hub back-office access.

How do I log a service request through Jentic?

Import the Generali Care Hub Backoffice API from the Jentic API Directory, then have your agent issue a request such as 'log a service request for this region'. Jentic matches the intent to the create-service-request operation and returns its input schema so the agent supplies the right fields, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.