Jiminny
Connect with Jiminny to access call recordings, transcripts, coaching insights, and conversation intelligence data.
Connect with Jiminny to access call recordings, transcripts, coaching insights, and conversation intelligence data.
Supports authentication: Bearer Token
Set up the agent connector
Section titled “Set up the agent connector”Register your Jiminny API key with Scalekit so it can authenticate requests to Jiminny’s conversation intelligence API on your behalf. You’ll need an API key from your Jiminny organisation settings.
-
Generate an API key in Jiminny
-
Sign in to Jiminny and navigate to Organisation Settings → General.
-
Scroll to the API Key section and click Generate API Key.
-
Click Copy to copy the key to your clipboard. Store it securely — you can regenerate it later, but doing so invalidates the previous key and breaks existing integrations.
-
-
Create a connection in Scalekit
In Scalekit dashboard, go to Agent Auth → Create Connection. Find Jiminny and click Create.
-
Add a connected account
Open the connection you just created and click the Connected Accounts tab → Add account. Fill in the required fields:
- Your User’s ID — a unique identifier for the user in your system
- Bearer Token — the API key you copied in step 1
Click Save.
Tool list
Section titled “Tool list”jiminny_action_items_get
Section titled “jiminny_action_items_get”Retrieve the AI-generated action items for a given activity, returning a list of follow-up tasks identified from the conversation.
| Name | Type | Required | Description |
|---|---|---|---|
activityId | string | Yes | The UUID of the activity to retrieve action items for. |
jiminny_activities_list
Section titled “jiminny_activities_list”Retrieve completed and processed call and meeting activities with optional date range, update date range, status, and page filters. The time range must be less than six months and you must provide either fromDate/toDate or updatedFrom.
| Name | Type | Required | Description |
|---|---|---|---|
fromDate | string | No | Filter activities that occurred after this UTC date-time (e.g. 2021-10-01 00:00:00). Must be before toDate. |
page | integer | No | Page number to return (page size is 500 activities). Default is 1. |
status | string | No | Filter activities by status: in-progress, completed (for calls/meetings), received, sent, delivered (for SMS/Voice dialer). |
toDate | string | No | Filter activities that occurred before this UTC date-time (e.g. 2021-11-01 00:00:00). Cannot be a future date. |
updatedFrom | string | No | Filter activities updated after this UTC date-time (e.g. 2021-11-01 00:00:00). Must be before updatedTo. |
updatedTo | string | No | Filter activities updated before this UTC date-time. Cannot be a future date. Defaults to current time. |
jiminny_activity_upload
Section titled “jiminny_activity_upload”Upload a call or meeting recording file to Jiminny for transcription and analysis, returning the new activity ID on success.
| Name | Type | Required | Description |
|---|---|---|---|
accountId | string | No | An optional CRM Account ID to associate with this activity (max 100 characters). |
completedAt | string | No | The date the activity was completed (format: YYYY-MM-DD). |
externalId | string | No | An optional external identifier for this activity (max 191 characters). Must be unique per host user. |
hostUserEmail | string | Yes | The email address of the host user. Must belong to the authenticated team. |
language | string | Yes | The language locale of the activity (e.g. en_GB, en_US, fr_FR). |
leadId | string | No | An optional CRM Lead ID to associate with this activity (max 180 characters). |
notifyForUploadCompletionByEmail | boolean | No | Whether to notify the host user via email when the upload and processing is complete. |
opportunityId | string | No | An optional CRM Opportunity ID to associate with this activity (max 100 characters). |
skipFullAnalysis | boolean | No | Whether to skip the full AI analysis of the uploaded activity. |
title | string | Yes | The title of the activity (max 250 characters). |
jiminny_automated_call_scoring_list
Section titled “jiminny_automated_call_scoring_list”Retrieve automated call scoring records with optional filters by user and date range, returning scores, activity types, and user details.
| Name | Type | Required | Description |
|---|---|---|---|
fromDate | string | No | Filter scoring records created after this UTC date-time (e.g. 2021-10-01 00:00:00). |
toDate | string | No | Filter scoring records created before this UTC date-time (e.g. 2021-11-01 00:00:00). Cannot be a future date. |
userId | string | No | Optional UUID of the user to filter automated call scoring results by. |
jiminny_coaching_feedback_list
Section titled “jiminny_coaching_feedback_list”Retrieve bulk coaching feedback records within a required date range, optionally filtered by coach or coachee, returning scores, activity IDs, and timestamps.
| Name | Type | Required | Description |
|---|---|---|---|
coachId | string | No | Optional UUID of the coach (manager) to filter coaching feedback by. |
coacheeId | string | No | Optional UUID of the coachee (sales rep) to filter coaching feedback by. |
fromDate | string | Yes | Filter coaching feedback records created after this UTC date-time (e.g. 2021-10-01 00:00:00). Must be before toDate. |
toDate | string | Yes | Filter coaching feedback records created before this UTC date-time (e.g. 2021-11-01 00:00:00). Cannot be a future date. |
jiminny_comments_list
Section titled “jiminny_comments_list”Retrieve activity comment records with optional filters by user and date range, returning comment IDs, activity IDs, user IDs, and creation timestamps.
| Name | Type | Required | Description |
|---|---|---|---|
fromDate | string | No | Filter comments created after this UTC date-time (e.g. 2021-10-01 00:00:00). Must be before toDate. |
toDate | string | No | Filter comments created before this UTC date-time (e.g. 2021-11-01 00:00:00). Cannot be a future date. |
userId | string | No | Optional UUID of the user to filter comments by. |
jiminny_listens_list
Section titled “jiminny_listens_list”Retrieve listened (played) activity records within a date range, optionally filtered by user, showing who listened to which activities and when.
| Name | Type | Required | Description |
|---|---|---|---|
fromDate | string | Yes | Filter listened activities that occurred after this UTC date-time (e.g. 2021-10-01 00:00:00). Must be before toDate. |
toDate | string | Yes | Filter listened activities that occurred before this UTC date-time (e.g. 2021-11-01 00:00:00). Cannot be a future date. |
userId | string | No | Optional UUID of the user to filter listened activities by. |
jiminny_organization_get
Section titled “jiminny_organization_get”Return the current authenticated Organization details including name, CRM integration, calendar type, and address.
jiminny_questions_get
Section titled “jiminny_questions_get”Retrieve questions detected in a specific activity, including their timestamps, speaker participant IDs, text, and whether they are engaging or insightful.
| Name | Type | Required | Description |
|---|---|---|---|
activityId | string | Yes | The UUID of the activity to retrieve detected questions for. |
jiminny_summary_get
Section titled “jiminny_summary_get”Get the AI-generated conversation summary for a given activity, returning the summary content text.
| Name | Type | Required | Description |
|---|---|---|---|
activityId | string | Yes | The UUID of the activity to retrieve the summary for. |
jiminny_topic_triggers_list
Section titled “jiminny_topic_triggers_list”Retrieve all topic triggers configured for the authenticated team, returned as a hierarchy of themes, topics, and trigger keywords.
jiminny_topic_triggers_matched_get
Section titled “jiminny_topic_triggers_matched_get”Retrieve all topic triggers that were matched within a specific activity, including the theme, topic, trigger keyword, timestamps, and matched text excerpt.
| Name | Type | Required | Description |
|---|---|---|---|
activityId | string | Yes | The UUID of the activity to retrieve matched topic triggers for. |
jiminny_transcript_get
Section titled “jiminny_transcript_get”Retrieve transcription segments for a given activity, returning an array of timed speech segments with speaker participant IDs.
| Name | Type | Required | Description |
|---|---|---|---|
activityId | string | Yes | The UUID of the activity to retrieve the transcription for. |
jiminny_users_list
Section titled “jiminny_users_list”Retrieve all users belonging to the authenticated team, including their IDs, names, emails, statuses, team names, CRM IDs, and roles.
jiminny_webhook_create
Section titled “jiminny_webhook_create”Create a webhook subscription that sends event payloads to a destination URL when a specified trigger occurs in Jiminny.
| Name | Type | Required | Description |
|---|---|---|---|
external_id | string | No | An optional external identifier for the webhook (max 191 characters). |
trigger | string | Yes | The event trigger for the webhook. One of: coaching_feedback_completed, conversation_shared, conversation_exported, conversation_processed, conversation_played. |
url | string | Yes | The destination URL to receive the webhook payload (max 191 characters). |
jiminny_webhook_delete
Section titled “jiminny_webhook_delete”Delete an existing webhook subscription by its UUID.
| Name | Type | Required | Description |
|---|---|---|---|
id | string | Yes | UUID of the webhook to delete. |
jiminny_webhook_sample_get
Section titled “jiminny_webhook_sample_get”Retrieve a sample webhook payload for a given trigger event type to understand the data structure that will be sent.
| Name | Type | Required | Description |
|---|---|---|---|
trigger | string | Yes | The webhook trigger event type to get a sample payload for. |