Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • System

REST API Wrappers for V1 Compatibility

Written by Mitchell Ivany

Updated at March 14th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Our Products & Services
  • Getting Started
    First Time Setup Baseline Configuration
  • Accounts
  • Communication
  • Billing
  • Companies
  • Financial
  • Integrations
  • Inventory
  • Jobs
  • ​Mapping
  • Misc.
  • Monitoring
  • Purchase Orders
  • Release Notes
  • Sonar Billing
  • Voice
  • Reporting
  • Security
  • sonarPay
  • Ticketing
  • Working With the Sonar Team & Additional Resources
    Sonar's Security Practices & Certifications
  • System
  • Networking
+ More

Table of Contents

Sonar V2 Supported Endpoints Testing the API wrapper Authenticating via Base64 username+password

While Sonar V2 uses GraphQL as its primary API language, rather than REST endpoints, many APIs that were available in Sonar V1 have been ported to V2 for backwards-compatibility purposes.

To see a list of all V1 endpoints, visit legacy.sonar.software/apidoc. There is also a subset of those V1 endpoints that are available in the current version of Sonar, which are listed below.

Sonar V2 Supported Endpoints

All supported endpoints will include the following base: https://example.sonar.software/api/v1

 
Category Index Show Create Update Delete
Account Addresses

Account Billing

Account Call Logs

Account Contacts

Account IP Addresses

Account Inventory

Account Invoices

Account Services

Account Tax Overrides

Accounts

Address Lists

Alerting Rotations

Contracts

DHCP Server Identifiers

DHCP Servers

Financial

General Ledger Codes

Inbound Email Accounts

Inline Devices

     
Inventory - Generic Assignee

Invoice Messages

IPAM – IP pool

Job Types

Jobs

Monitoring Templates – Threshold

Network Site IP Addresses

Network Sites – Site

Notes

Radius Account

Rate Centers

Roles

     
Packages

Scheduled Events

Services

System

Task Templates

Tasks

Ticket Groups

Usage Based Billing - Free Period

Users

Voice Providers

Testing the API wrapper

This cURL example assumes the username is apiguy and the password is superSecret123:

  1. bash/zsh/etc example (e.g., Linux or Mac):
API_URI=https://myinstance.sonar.software/api/v1/system/services
API_USER=apiguy
API_PASSWORD='superSecret123'

curl --basic --user "$API_USER":"$API_PASSWORD" $API_URI
  1. Windows cmd/PowerShell:
curl.exe --basic --user apiguy:"superSecret123" https://myinstance.sonar.software/api/v1/system/services

Authenticating via Base64 username+password

If you’re using software you have written yourself, you may need to convert the username and password into an http basic authentication string. To do this, concatenate username:password. For example, if your username is apiguy and your password is superSecret123, convert apiguy:superSecret123 to base64 encoding. You can paste them below and we will do it for you. Note that nothing is transmitted to our server--this runs in your own web browser only.


Username: Password:
api compatibility rest wrappers

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • API Calls Using Third Party Applications: Personal Access Tokens
  • Consuming the Sonar API
  • Controlling Your Landing Page: Personal Preferences
Expand