canonical: https://jentic.com/apis/generalicarehub.com/generalicarehub

# Generalicarehub SDD Backoffice API

The Generali Care Hub Backoffice API runs the operational back office for a service-assistance network, centred on service requests that are logged, tracked, and resolved by a service provider. It holds the records the dispatch side depends on: service providers, drivers and their vehicles, the regions and region points they cover, and the companies and contracts that back each service. It also collects customer rating forms once a service is done, and manages the service definitions and forms used across the network.

## For AI agents

Log and track service requests, register service providers, drivers, and vehicles, and assign providers to regions in a service-assistance network. Authenticates with a bearer token.

## Scope

Does not handle payment settlement, insurance claims, or vehicle telematics. Use for managing service requests, providers, and the dispatch network only.

## Capabilities

- Create and track service requests from the moment they are logged
- Register service providers, drivers, and their vehicles
- Assign service providers to the regions they cover
- Organize the network into regions, region points, and partitions
- Record the companies and contracts behind each service
- Collect customer rating forms and maintain the service forms used

## Use cases

### Agent-Logged Service Requests

An AI agent connected through Jentic logs a new service request against a region and reads back its status as it moves toward resolution, so intake does not wait on a back-office operator. Because the agent works against the same service-request records the dispatch team uses, the request is visible to the network right away.

Example prompt: Create a service request for the given region and return its id and status

### Provider and Fleet Onboarding

An operations workflow registers a new service provider, adds their drivers and driver vehicles, and assigns the provider to the regions they cover, so the network knows who can be dispatched where. Keeping providers, drivers, vehicles, and region coverage in one back office means a dispatcher can trust the roster when routing a request.

Example prompt: Register a service provider, add a driver and vehicle, and assign the provider to a region

### Post-Service Rating Collection

After a service request is resolved, a workflow records a customer rating form against it, so feedback is captured in the same system that tracked the request. This keeps the rating tied to the request and provider it refers to rather than a separate survey tool.

Example prompt: Submit a customer rating form for a completed service request

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/service-requests` | Create a service request |
| GET | `/service-requests` | List service requests |
| POST | `/service-providers` | Register a service provider |
| POST | `/drivers` | Register a driver |
| POST | `/service-provider-regions` | Assign a provider to a region |
| POST | `/customer-rating-forms` | Submit a customer rating form |
| GET | `/regions` | List regions |
| POST | `/contracts` | Create a contract |

## Key resources

- **Service Requests** — Assistance requests logged, tracked, and resolved by a service provider
- **Service Providers** — Providers, their drivers, and driver vehicles available for dispatch
- **Regions** — Regions, region points, and partitions that organize coverage
- **Companies and Contracts** — Companies and the contracts that back the services offered
- **Customer Rating Forms** — Feedback forms captured against a completed service

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 15 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 43 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 5 / 100
  - Agent Usability: 77 / 100
  - Security: 75 / 100
  - AI Discoverability: 15 / 100
- **View full report:** https://jentic.com/apis/generalicarehub.com/generalicarehub/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Generali Care Hub Backoffice API by hand means obtaining a JSON Web Token through its local login operations, sending it as a bearer token on each call, and threading service requests, providers, and regions together yourself. Through Jentic you install once, import the API from the Directory, store the token once, and your agent calls it.
- **Permission scoping:** You choose which operations your agent may call, so you can allow creating and reading service requests while leaving provider, contract, and region changes out. Destructive operations like deleting a service provider or a contract are not included unless you add them, and every call is logged.
- **Credential handling:** Your Generali Care Hub token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'log a service request' or 'assign a provider to a region', and Jentic returns the matching Generali Care Hub operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Zoho FSM API** — Field service management platform for dispatching technicians to work orders
- **ServiceNow API** — Service management platform for tracking and routing service requests at scale
- **Zendesk API** — Support platform for managing customer requests as tickets
- **Twilio Messaging API** — Sends the SMS and WhatsApp messages the back office configures senders for

## FAQ

### Is there a Generali Care Hub MCP server?

You don't need an MCP server to give your agent the Generali Care Hub Backoffice API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can log service requests and read their status straight away, with no extra server to run and no tool definitions to load into the agent's context.

### 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.