canonical: https://jentic.com/apis/sales.app.redkik.com/sales-app-redkik

# Sales App Redkik userservice

Redkik is a global InsurTech company with the mission to transform and improve the insurance industry for all parties within logistics and transportation. Redkik's innovative software eliminates the need for annual and complex insurance policies. Through Redkik's embedded integration with licensed insurance providers, existing platforms and online systems can offer their customers tailored and tra. The API exposes 60 endpoints secured with bearer authentication.

## For AI agents

Programmatically apitokencontroller_createuserapitoken, apitokencontroller_deletebyid. Covers 60 operations with bearer authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- ApiTokenController_createUserApiToken
- ApiTokenController_deleteById
- AuditController_createUserAudits
- AuditController_getAudits
- Authentications_authorizeOauthUser
- Authentications_getForgottenOauth
- Authentications_postOauthLogin

## Use cases

### Payments Operations

Use the userservice to perform payments operations programmatically. The API provides 60 endpoints covering core functionality including apitokencontroller_createuserapitoken, apitokencontroller_deletebyid, auditcontroller_createuseraudits.

Example prompt: Call POST `/api/v2/user/api-tokens` to apitokencontroller_createuserapitoken

### Automated OrganizationController Management

Automate organizationcontroller operations by combining multiple userservice endpoints. Agents can apitokencontroller_deletebyid and then auditcontroller_createuseraudits in a single workflow.

Example prompt: Call DELETE `/api/v2/user/api-tokens/{id}` to apitokencontroller_deletebyid, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call userservice endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'apitokencontroller_createuserapitoken', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v2/user/api-tokens` | ApiTokenController_createUserApiToken |
| DELETE | `/api/v2/user/api-tokens/{id}` | ApiTokenController_deleteById |
| POST | `/api/v2/user/audits` | AuditController_createUserAudits |
| GET | `/api/v2/user/audits` | AuditController_getAudits |
| GET | `/api/v2/user/oauth/authorize` | Authentications_authorizeOauthUser |
| GET | `/api/v2/user/oauth/forgotten` | Authentications_getForgottenOauth |
| POST | `/api/v2/user/oauth/auth/login` | Authentications_postOauthLogin |
| POST | `/api/v2/user/oauth/auth/reset` | Authentications_resetOauthToken |

## Key resources

- **OrganizationController** — Operations related to OrganizationController
- **UserController** — Operations related to UserController
- **Authentications** — Operations related to Authentications
- **RoleController** — Operations related to RoleController
- **ApiTokenController** — Operations related to ApiTokenController

## Why Jentic

- **Setup:** Wiring the Redkik userservice API by hand means learning its bearer auth, managing your own API tokens against the sales.app.redkik.com host, and handling token lifecycle and retries yourself. Through Jentic you install once, import userservice from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** This API puts the token id in the URL path (`/api/v2/user/api-tokens/{id}`), so a rule can pin your agent to one token record: it can read or create what you allow and nothing else. You choose the operations it may call, so destructive ones like deleting an API token are not included unless you add them.
- **Credential handling:** Your Redkik bearer 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 'create a user API token' or 'list user audits', and Jentic returns the matching userservice operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the userservice use?

The userservice uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I apitokencontroller_createuserapitoken with the userservice?

Yes. Use the POST `/api/v2/user/api-tokens` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the userservice?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I apitokencontroller_createuserapitoken through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'apitokencontroller_createuserapitoken'. Jentic returns the matching userservice operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the userservice have?

The userservice exposes 60 endpoints covering organizationcontroller, usercontroller, authentications operations.

### Can I limit what my agent is allowed to do with the Redkik userservice API?

Yes. Jentic One is self-hosted by you, so your own rules decide which userservice operations and credentials the agent may use. Because this API carries the token id in the URL path (`/api/v2/user/api-tokens/{id}`), you can pin the agent to a single token record and let it read or create only what you permit. You choose the operations it can call, so destructive ones such as DELETE `/api/v2/user/api-tokens/{id}` stay off limits unless you explicitly add them.