Numeracle API’s is a reliable and efficient solution for organizations seeking to harness the power of phone number related information.
\nNumeracle employs OAuth 2.0 for authentication. To execute the API, you’ll require a bearer
token. Generate this token using the provided Client ID and secret. Below is an
example of how to create the bearer token.
curl -X POST https://www.sandbox.numeracle.com/oauth/token \\
\n-H \"Content-Type: application/x-www-form-urlencoded\" \\
\n-u : \\<**YOUR_CLIENT_ID**>:<**YOUR_CLIENT_SECRET**>\\
\n-d \"grant_type=client_credentials”
\nRemember to replace YOUR_CLIENT_ID and YOUR_CLIENT_SECRET with your actual credentials.
\nNote: The validity of bearer token is around 9 hrs approx. , If you encounter an unauthorized error,please generate a new token with client ID and client secret.
\nhttps://www.sandbox.numeracle.com
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"Why Choose Numeracle API's:","slug":"why-choose-numeracle-apis"}],"owner":"39598180","collectionId":"c5bd7041-cec4-4844-b802-1b078f0240a1","publishedId":"2sBYHRTgG3","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2026-10-12T04:01:22.000Z"},"item":[{"name":"oauth","item":[{"name":"token","item":[{"name":"Sandbox Token","id":"e23007fb-2794-4f96-aee7-3c8d17f7e5e4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"auth":{"type":"basic","basic":{"basicConfig":[{"key":"username","value":"Note: The validity of the bearer token is around 9 hours.
If you encounter an unauthorized error, please generate a new token with the client ID and client secret.
Fetches the list of Originating Service Providers (OSPs) currently available.
\nUpdates the list of Originating Service Providers (OSPs) assigned to a Entity.
\nEnables or disables the sVIP feature for a specific entity. This controls whether the entity can participate in sVIP operations such as Number Profile management, CDR processing, and OSP assignment.
\nAdds a Number Profile to the sVIP system for a specific entity. This allows the number to be associated with the numberprofile and tracked under sVIP, with optional attestation status.
\nResponse Parameters
\n","urlObject":{"protocol":"https","path":["api","v1","svip","number-profile"],"host":["www","sandbox","numeracle","com"],"query":[],"variable":[]}},"response":[{"id":"b9865016-255b-451b-9963-84f268fac318","name":"200-OK","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"BearerRemoves a Number Profile from the sVIP system. This action permanently deletes the profile along with its associated phone numbers.
\nBusiness Validations
\nRetrieves detailed information about an enterprise (entity) in the sVIP system. This includes basic entity information such as the entity name, internal entity ID (eid), and other metadata. Useful for auditing, display, or integration purposes.
Path Variable
\nBusiness Validation
\nThe CDR API retrieves a list of Call Detail Records (CDRs) for entities in the sVIP system. These records provide detailed information about calls associated with an entity, including originating and destination numbers, originating service provider (OSP), number profiles, claims status, and audit-related metadata.
\n10 hits per 10 minutes per source IP address.
\nExceeding this limit returns HTTP 429. Wait for the rolling 10-minute window to allow more requests, then retry.
\nlimit remains 1–1000 (typically 1000). Rate limiting applies to the HTTP request count, not the number of CDR rows returned.
Response Parameters
\n