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 Targets API

The Customer Targets API from Nfon — 29 operation(s) for customer targets.

Documentation Provider Profile APIs.io OpenAPI GitHub

Nfon Customer Targets 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 Targets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 44 operations across 29 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 2026.07.20.

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

44 operations 29 paths 24 schemas 7 DELETE28 GET7 POST2 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 Targets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (jwt).

Paths & Operations 44

Across 29 paths, the API surfaces 44 operations — 7 DELETE, 28 GET, 7 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Customer Targets 44
GET
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}/inbound-trunk-numbers
Get 95
get_95 2 params → 200403
POST
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}/inbound-trunk-numbers
Post 26
post_26 2 params body → 403400201
GET
/tenants/{participantExternalIdentifier}/targets/routing-prefix
Get 88
get_88 1 param → 200403
POST
/tenants/{participantExternalIdentifier}/targets/routing-prefix
Post 23
post_23 1 param body → 403400201
PUT
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}
Put 27
put_27 2 params body → 404204400403
DELETE
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}
Delete 22
delete_22 2 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}
Get 89
get_89 2 params → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/devices
Get 61
get_61 2 params → 200403404
POST
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/devices
Post 14
post_14 2 params body → 403400201
DELETE
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/devices/{uniqueIdentifier}
Delete 14
delete_14 3 params → 404204403
DELETE
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/inbound-trunk-numbers/{didNumber}
Delete 23
delete_23 3 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/inbound-trunk-numbers/{didNumber}
Get 91
get_91 3 params → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/outbound-trunk-numbers
Get outbound trunk numbers with page 1
getOutboundTrunkNumbersWithPage_1 2 params → 200403404
POST
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/outbound-trunk-numbers
Post outbound trunk numbers 1
postOutboundTrunkNumbers_1 2 params body → 403400201
GET
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/outbound-trunk-numbers/available-trunks
Get available trunks 1
getAvailableTrunks_1 2 params → 200403404
DELETE
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/outbound-trunk-numbers/{outboundTrunkNumberId}
Delete outbound trunk number 1
deleteOutboundTrunkNumber_1 3 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/outbound-trunk-numbers/{outboundTrunkNumberId}
Get outbound trunk numbers 1
getOutboundTrunkNumbers_1 3 params → 200403404
GET
/tenants/{participantExternalIdentifier}/targets
Get 174
get_174 1 param → 200403
GET
/tenants/{participantExternalIdentifier}/targets/BUSY
Get 166
get_166 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/HANGUP
Get 169
get_169 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/INTERNAL_SOURCE
Get 170
get_170 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/OWN_VOICEMAIL
Get 172
get_172 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/REPEAT
Get 173
get_173 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/VOICEMAILSERVICE
Get 175
get_175 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions
Get 93
get_93 1 param → 200403
POST
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions
Post 25
post_25 1 param body → 403400201
GET
/tenants/{participantExternalIdentifier}/targets/NO_ACTION
Get 171
get_171 1 param → 200403404
PUT
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}
Put 29
put_29 2 params body → 404204400403
DELETE
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}
Delete 24
delete_24 2 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}
Get 94
get_94 2 params → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/direct-dial/{directDialNumber}
Get 167
get_167 3 params → 200403404
DELETE
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}/inbound-trunk-numbers/{didNumber}
Delete 25
delete_25 3 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}/inbound-trunk-numbers/{didNumber}
Get 96
get_96 3 params → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/routing-prefix/available-devices
Get 59
get_59 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}/outbound-trunk-numbers
Get outbound trunk numbers with page 2
getOutboundTrunkNumbersWithPage_2 2 params → 200403404
POST
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}/outbound-trunk-numbers
Post outbound trunk numbers 2
postOutboundTrunkNumbers_2 2 params body → 403400201
GET
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}/outbound-trunk-numbers/available-trunks
Get available trunks 2
getAvailableTrunks_2 2 params → 200403404
DELETE
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}/outbound-trunk-numbers/{outboundTrunkNumberId}
Delete outbound trunk number 2
deleteOutboundTrunkNumber_2 3 params → 404204403
GET
/tenants/{participantExternalIdentifier}/targets/virtual-fax-extensions/{extensionNumber}/outbound-trunk-numbers/{outboundTrunkNumberId}
Get outbound trunk numbers 2
getOutboundTrunkNumbers_2 3 params → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/external/{externalNumber}
Get 168
get_168 3 params → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/inbound-trunk-numbers
Get 90
get_90 2 params → 200403
POST
/tenants/{participantExternalIdentifier}/targets/routing-prefix/{extensionNumber}/inbound-trunk-numbers
Post 24
post_24 2 params body → 403400201
GET
/tenants/{participantExternalIdentifier}/targets/ANY_SOURCE
Get 165
get_165 1 param → 200403404
GET
/tenants/{participantExternalIdentifier}/targets/ANONYMOUS_SOURCE
Get 164
get_164 1 param → 200403404

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are VirtualFaxExtensionData (11 properties), POSTData (7 properties), NfonApiCollectionResponsePage (6 properties), Short (6 properties). Each schema is shown below with its type and property counts.

InboundTrunkNumberData
object
1 property
PUTLinks
object
2 properties
OutboundTrunkNumberData
object
PUTData
object
3 properties
NfonApiResponse
object
Standard API response envelope for a single resource
3 properties
POSTData
object
7 properties
POSTRequest
object
4 properties
NfonApiCollectionResponsePage
object
Paginated collection response envelope
6 properties
Links
object
Related resource links
NfonApiCollectionResponseNonPage
object
Non-paginated collection response envelope
3 properties
InboundTrunkNumberRequest
object
4 properties
OutboundTrunkNumberLinks
object
InboundTrunkNumberLinks
object
1 property
VirtualFaxExtensionLinks
object
5 properties
Boolean
object
6 properties
OutboundTrunkNumberRequest
object
4 properties
VirtualFaxExtensionRequest
object
4 properties
String
object
Link to the last page
6 properties
CollectionLinks
object
Pagination links for collection responses
4 properties
PUTRequest
object
4 properties
Short
object
6 properties
RoutingPrefixExtensionLinks
object
2 properties
VirtualFaxExtensionData
object
11 properties
NfonApiCollectionResponse
object
Collection response envelope

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nfon-customer-targets-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 Targets
← Back to N APIs
API Details
ID
nfon:nfon-customer-targets-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-targets-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/nfon-customer-targets-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 Targets 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.