The NFON Call History API provides endpoints for retrieving, streaming, and deleting call history records for an authenticated NFON Cloud Telephony user.
Important
This API is currently offered as part of Login with NFON (Early Access).
As an early access offering, the API is subject to change. Updates may occur on short notice, though we strive to provide advance notice where possible.
- Retrieve call history records for an extension with filtering and search capabilities
- Stream real-time call history events as they occur using Server-Sent Events (SSE)
- Access call transcriptions and summaries for answered calls
- Delete call records individually or in bulk based on various criteria
- Integrate call history data into CRM systems or custom applications
By accessing and using the NFON Call History API, you agree to the terms of use.
API endpoints may change:
- Please subscribe to
API Breaking Changeson the NFON Status page for updates. - Please refer to the latest API documentation.
NFON is committed to helping you integrate successfully with our APIs. Depending on the type of request or issue, please use the following channels:
Got ideas to improve the API? Submit feature suggestions via Airfocus:
For best practices, implementation guidance, and community support:
- Join the NFON Partner Portal
- Contact your assigned sales representative
For technical issues or suspected bugs, please contact NFON Support directly.
Check the official API documentation for latest endpoint references.
- Base URL:
https://api.nfon.com/call-history - Architecture: RESTful API
- Data Format: JSON
Get, search, and stream call records with optional filtering.
The response format is controlled by the Accept request header:
application/json(default): Returns a JSON array of call recordstext/event-stream: Streams call records as Server-Sent Events (SSE)
Delete multiple call records based on filter criteria.
Get details for a specific call record.
Delete a single call record.
The NFON Call History API uses an OAuth 2.0 Access Token obtained via a browser-based login to NFON Cloud Telephony applications like the Cloudya Web app.
The Access Token must be included with every API request.
💡 As part of the Login with NFON (Early Access), NFON provides partners with their own OAuth client, enabling them to integrate directly with the NFON login system using the standard OAuth 2.0 Authorization Code flow with PKCE.
Authentication Header:
Authorization: Bearer <your-access-token>
Access Token
│
▼
GET /call-history/records
(Authorization)
This example API call fetches call history entries.
curl 'https://api.nfon.com/call-history/records?limit=25' \
-H 'accept: application/json' \
-H 'authorization: Bearer <ACCESS_TOKEN>' \
-H 'user-agent: my-crm-app/1.5.1'When integrating with the NFON APIs, please include a User-Agent header in all HTTP requests with the following format:
<productname>/<productversion>
Example:
my-crm-app/1.5.1
Including your application name and version in the User-Agent helps NFON's technical support team:
- Quickly identify your application in case of issues or unusual activity
- Provide faster support by understanding which integration is affected
- Contact you proactively if we detect any problems with your integration
All code examples in this repository include configurable constants at the top of each file:
const (
appName = "NFON-GitHub-Example" // Replace with your application name
appVersion = "1.0" // Replace with your application version
)Simply update these values to match your application before deploying to production.
Below you'll find working examples for API operations using various programming languages. These are designed to help you get started quickly and understand how to authenticate and interact with the NFON Call History API.
Tip
Cannot find your programming language of choice? We recommend you to use an AI assistant to rewrite the examples to other programming languages.