How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Nfon

Nfon Customer Queues API

The Customer Queues API from Nfon — 12 operation(s) for customer queues.

Documentation Provider Profile APIs.io OpenAPI GitHub

Nfon Customer Queues API is one of 52 APIs that Nfon publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customer Queues. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 23 operations across 12 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 2026.07.20.

Requests are made against a single base URL, /configuration/v1.

23 operations 12 paths 26 schemas 4 DELETE12 GET3 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026.07.20
Base URL
https://api.nfon.net/configuration/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Nfon Customer Queues API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwt).

Paths & Operations 23

Across 12 paths, the API surfaces 23 operations — 4 DELETE, 12 GET, 3 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Customer Queues 23
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/available-destinations-on-rejection
get_146 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/available-general-announcements
get_142 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/available-music-on-hold-announcements
get_143 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/members
get_150 2 params → 200403
POST
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/members
post_46 2 params body → 403400201
PUT
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/members/{extensionNumber}
put_45 3 params body → 404204400403
DELETE
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/members/{extensionNumber}
delete_46 3 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/members/{extensionNumber}
get_151 3 params → 200403404
PUT
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/timeout
put_52 2 params body → 404204400403
DELETE
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/timeout
delete_52 2 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/timeout
get_182 2 params → 200403404
PUT
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}
put_41 2 params body → 404204400403
DELETE
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}
delete_42 2 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}
get_135 2 params → 200403404
DELETE
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/inbound-trunk-numbers/{didNumber}
delete_43 3 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/inbound-trunk-numbers/{didNumber}
get_137 3 params → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/inbound-trunk-numbers
get_136 2 params → 200403
POST
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/inbound-trunk-numbers
post_43 2 params body → 403400201
GET
/tenants/{participantExternalIdentifier}/targets/queue-services
get_134 1 param → 200403
POST
/tenants/{participantExternalIdentifier}/targets/queue-services
post_42 1 param body → 403400201
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/destination-on-rejection
get_148 2 params → 200403404
PUT
/tenants/{participantExternalIdentifier}/targets/queue-services/{serviceNumber}/destination-on-rejection
put_43 2 params body → 404204400403
GET
/tenants/{participantExternalIdentifier}/targets/queue-services/available-destinations-on-timeout
get_178 1 param → 200403404

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are QueueData (18 properties), QueueLinks (13 properties), Integer (6 properties), String (6 properties). Each schema is shown below with its type and property counts.

TimeoutRequest
object
4 properties
QueueMemberLinks
object
1 property
InboundTrunkNumberRequest
object
4 properties
NfonApiCollectionResponseNonPage
object
Non-paginated collection response envelope
3 properties
Links
object
Related resource links
DestinationOnRejectionRequest
object
4 properties
Integer
object
Subscribers soft limit
6 properties
CollectionLinks
object
Pagination links for collection responses
4 properties
RequestLinks
object
1 property
QueueData
object
18 properties
QueueMemberData
object
3 properties
ChildHref
object
String
object
Link to the last page
6 properties
Boolean
object
6 properties
InboundTrunkNumberLinks
object
1 property
QueueMemberRequest
object
4 properties
NfonApiCollectionResponse
object
Collection response envelope
QueueLinks
object
13 properties
Enum
object
6 properties
NfonApiCollectionResponsePage
object
Paginated collection response envelope
6 properties
TimeoutLinks
object
Date
object
6 properties
NfonApiResponse
object
Standard API response envelope for a single resource
3 properties
InboundTrunkNumberData
object
1 property
Data
object
Data represents key-value pair for additional reference metadata.
2 properties 2 required
QueueRequest
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nfon-customer-queues-api-openapi.yml Raw ↑

Other APIs Nfon publishes across the network.

NFON Service Portal API (legacy)
AE Profile APIs.io
Nfon Accounts API
AE Profile APIs.io
Nfon address API
AE Profile APIs.io
Nfon authentication API
AE Profile APIs.io
Nfon Blacklist Profiles API
AE Profile APIs.io
Nfon clip-screened-prefixes API
AE Profile APIs.io
Nfon Contract Types API
AE Profile APIs.io
Nfon Customer Announcements API
AE Profile APIs.io
Nfon Customer Conference API
AE Profile APIs.io
Nfon Customer Contracts API
AE Profile APIs.io
Nfon Customer Device Types API
AE Profile APIs.io
Nfon Customer Devices API
AE Profile APIs.io
#Customer Queues
← Back to N APIs
API Details
ID
nfon:nfon-customer-queues-api
Base URL
https://api.nfon.net/configuration/v1
Docs
https://www.nfon.com/en/integrations/api
Provider
Nfon
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=nfon-customer-queues-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/nfon-customer-queues-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Nfon Customer Queues API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.