Voice & Callingx-api-key + Authorization keyConfirm pricing before publishing
Knowlarity
Indian cloud telephony for click-to-call bridges and transfers.
AProvider definition
- Provider
- Knowlarity
- What it does
- Indian cloud telephony for click-to-call bridges and human transfers.
- Why we need it
- Indian cloud telephony for click-to-call bridges and transfers.
- Used in
- AI Calling (transfers) · CRM click-to-call
- AI capabilities
- telephony
- Official site
- https://www.knowlarity.com
BAccount requirements
- Account type
- Knowlarity SuperReceptionist account
- Prerequisites
- KYC-verified business
- SR number
CConnection method
- Authentication
- x-api-key + Authorization key
- Where to enter it
- Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
Setup steps
- 1Request API access from your Knowlarity account manager.
- 2Copy the x-api-key, Authorization key and SR number.
- 3Enter them with your caller ID.
DPermissions & API scopes
No OAuth scopes — access is controlled by the key or token itself. Restrict keys to the APIs listed in the setup steps where the provider allows it.
This list is generated from the scopes the application's code requests.
EFree vs paid
- Free account / free API access
- Check the provider's pricing page.
- Card or billing account required?
- Usually required for production use.
- Paid plan / costs
- Plan-based.
- Quota and usage limits
- Provider-specific rate limits.
Not yet verified. Confirm on the provider's official pricing page before publishing.
FSetup screenshots
Capture each step with real values masked. Save images as public/docs/integrations/knowlarity/1.png … 10.png and they appear here automatically.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Not applicable3. Project / app creationCreating the app or project used for this integration.
- Not applicable4. API enablementThe API or product enabled for the project.
- Not applicable5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Not applicable7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe green Test result or the connected account listed.
GApplication configuration
Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.
| Field | Required | Example / default | Notes |
|---|---|---|---|
| x-api-key | Yes | •••••••• | Stored encrypted; shown masked after saving. |
| Authorization key | Yes | •••••••• | Stored encrypted; shown masked after saving. |
| SuperReceptionist number (k_number) | Yes | — | |
| Caller ID | Yes | — |
HTesting
- 1Saved without a live check — place one click-to-call from a lead to verify.
ITroubleshooting
| Problem | What to do |
|---|---|
| Invalid credentials | The key or token is wrong, revoked or from another project. Create a new one and paste it again, then click Test. |
| Missing permissions | The key's project or role doesn't include this API. Grant access or create the key in the right project. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| Billing required | Add a payment method or prepaid credits on the provider account (see section E). |
JDisconnect & security
- Revoke access at the provider
- Ask Knowlarity to rotate the keys.
- Disconnect in the application
- App → Integrations → Providers & API keys → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
- Rotate credentials
- Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
- How credentials are stored
- Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
- What data the application can access
- Call metadata.

