Home Features API Hub Number API Calls

API Directory — Full Call Reference

Reference for the PBXMe API calls documented in the supplied Postman collection, plus separately identified operational endpoints. The documented platform calls use HTTP POST unless noted. Authenticate first with Login, then use the returned account values and generated session authentication as required by each call.

Base URL: https://newsip.pbxme.com

Authentication

Login

Endpoint: https://newsip.pbxme.com/api/login/

Before using the API, whitelist the source IP address of the server making requests in the user’s account portal. Each account has its own username and password. For the initial Login request, use those credentials together with the fixed x-auth-token published in the API documentation. A successful Login returns the account id, account_token, and a generated session x-auth-token. Use the generated session x-auth-token in the request header for subsequent calls in the same API session, and send the returned id and account_token in request bodies as the documented id and token values.

VariableDescription
usernameYour PBXMe account number
passwordYour PBXMe account password

Example Request:

POST https://newsip.pbxme.com/api/login/
x-auth-token: YOUR_INITIAL_X_AUTH_TOKEN
Content-Type: application/json

{
  "username": "YOUR_ACCOUNT_NUMBER",
  "password": "YOUR_PASSWORD"
}

⚠️ Save the returned id, account_token, and generated session x-auth-token. Use the session x-auth-token in the header of subsequent API calls, and use the returned id and account_token in request bodies as id and token.

Account

Charges History

Endpoint: {{URL}}/api/charges_history/get_charges_history_list/

Returns the charge history for the authenticated account.

VariableDescription
idAccount ID returned by Login
tokenaccount_token returned by Login
numberYour account number

Example Request:

{
  "id": "{{id}}",
  "token": "{{token}}",
  "number": "{{account_number}}"
}

CDRs Export

Endpoint: https://newsip.pbxme.com/api/cdrs_export

Generates a Call Detail Records (CDR) report for the requested date range. Following the API request, the report is sent to the email address registered on the account. The email includes a ZIP file attachment containing the CDR report in Excel format.

VariableDescription
idAccount ID
tokenaccount_token
from_dateStart date and time
to_dateEnd date and time

DID (Number) Management

Get Country List Disabled in Current Reference

The current API reference marks this call as disabled and provides the complete country list in its example. Use the numeric country_id from that reference when calling DID Available List.

DID Available List

Endpoint: {{URL}}/customer/did_crud/

Returns available numbers for a selected country.

VariableDescription
actionavailable_list
parent_idStatic value “0”
country_idOptional numeric country ID from the Country List reference
idAccount ID
tokenaccount_token

DID Assign

Endpoint: {{URL}}/customer/did_management/

Purchases and assigns a DID to your account.

VariableDescription
actionassign
did_idDID ID from Available List
accountidYour account ID
reseller_idStatic value “0”
idYour account ID
tokenaccount_token

DID Purchased List

Endpoint: {{URL}}/customer/did_crud/

Returns the DIDs currently assigned to your account.

VariableDescription
actionpurchase_list
idAccount ID returned by Login
tokenaccount_token returned by Login

DID Release

Endpoint: {{URL}}/customer/did_management/

Releases a DID from your account.

VariableDescription
actionrelease
did_idDID ID to release
accountidAccount ID returned by Login
idAccount ID returned by Login
tokenaccount_token returned by Login

DID Forward Setting

Endpoint: {{URL}}/customer/did_management/

Updates the call-routing/forwarding settings for a DID. The supplied API example demonstrates call_type=2 with a trunk IP in call_type_value. This call is a telephony forwarding configuration API and should not be treated as a generic HTTP event-webhook API.

VariableDescription
idAccount ID returned by Login
tokenaccount_token returned by Login
actionforward
did_idDID ID from the Purchased List
call_typeDocumented example uses static value 2
call_type_valueDocumented example uses your trunk IP
alwaysDocumented example uses static value 5
user_busyDocumented example uses static value 5
user_not_registeredDocumented example uses static value 5
no_answerDocumented example uses static value 5
extensionsMandatory field; documented example uses an empty value
call_type_vm_flagMandatory field; documented example uses an empty value
always_destinationMandatory field; documented example uses an empty value
always_vm_flagMandatory field; documented example uses an empty value
user_busy_destinationMandatory field; documented example uses an empty value
user_busy_vm_flagMandatory field; documented example uses an empty value
user_not_registered_destinationMandatory field; documented example uses an empty value
user_not_registered_vm_flagMandatory field; documented example uses an empty value
no_answer_destinationMandatory field; documented example uses an empty value
no_answer_vm_flagMandatory field; documented example uses an empty value

SMS Configuration

All SMS config calls use the endpoint: https://newsip.pbxme.com/api/sms

SMS Config Add

Creates an SMS forwarding configuration for an SMS-enabled number. Forwarding can be configured to another SMS number, email address, or webhook URL. For webhook-only forwarding, dest_sms and dest_email may be omitted.

VariableDescription
actionadd
idAccount ID returned by Login
tokenaccount_token returned by Login
didSMS-enabled number
dest_smsOptional SMS forwarding destination
dest_emailOptional email forwarding destination
webhook_urlOptional HTTP webhook destination

SMS Config Update

Updates an existing SMS forwarding configuration. SMS forwarding settings can be managed either through the API or from the account HTTP portal.

VariableDescription
actionupdate
idAccount ID returned by Login
tokenaccount_token returned by Login
didSMS-enabled DID
dest_smsOptional SMS forwarding destination
dest_emailOptional email forwarding destination
webhook_urlOptional HTTP webhook destination

SMS Config Delete

VariableDescription
actiondelete
idAccount ID returned by Login
tokenaccount_token returned by Login
didDID whose SMS forwarding configuration should be deleted

Get SMS Config

VariableDescription
actionget
idAccount ID returned by Login
tokenaccount_token returned by Login
didDID whose SMS forwarding configuration should be returned

SMS Config List

VariableDescription
actionlist
idAccount ID returned by Login
tokenaccount_token returned by Login

Outbound SMS — Separate Operational Endpoint

This endpoint is operational but is not part of the supplied Postman collection.

Send Outbound SMS Separate API

Endpoint: https://api.pbxme.com/astppsend-sms

Sends an outbound SMS through the PBXMe network. This call uses HTTP GET rather than the POST pattern used by the documented Newsip API calls.

VariableDescription
usernameYour PBXMe account username / account number
passwordYour account password
destinationDestination phone number
calleridSender / caller ID value permitted for your account
messageSMS message text
smsSMS mode parameter required by the endpoint
whatsappWhatsApp mode parameter supported by the endpoint

Your source IP must be configured under My Account → IP Settings. Because this endpoint is outside the supplied Postman collection, treat its parameter requirements as a separate operational API contract.

Example Request URL:

https://api.pbxme.com/astppsend-sms
  ?username=YOUR_ACCOUNT
  &password=YOUR_PASSWORD
  &destination=DESTINATION_NUMBER
  &callerid=YOUR_CALLER_ID
  &message=Hello
  &sms=1
  &whatsapp=0

Inbound SMS → Webhook Available Now

Incoming SMS can be forwarded to your own HTTP endpoint and the destination can be configured programmatically through POST /api/sms using webhook_url. The same SMS forwarding settings can also be configured from the account HTTP portal under Forward Type → API.

URL template: https://example.com/api?from={CallerID}&text={SMS_TEXT}&to={SMS_DST_ADDR}

PlaceholderLive value
{CallerID}Sender phone number
{SMS_TEXT}Inbound SMS message text
{SMS_DST_ADDR}The SMS-enabled PBXMe destination number

API configuration example:

POST https://newsip.pbxme.com/api/sms
x-auth-token: YOUR_SESSION_X_AUTH_TOKEN
Content-Type: application/json

{
  "action": "add",
  "id": "YOUR_ACCOUNT_ID",
  "token": "YOUR_ACCOUNT_TOKEN",
  "did": "YOUR_SMS_ENABLED_DID",
  "webhook_url": "https://example.com/api?from={CallerID}&text={SMS_TEXT}&to={SMS_DST_ADDR}"
}

SMS-to-webhook configuration is available both through the API and through the account HTTP portal. For webhook-only forwarding, dest_sms and dest_email may be omitted.

Quick Reference — All API Calls

CallEndpointPurpose
Login/api/login/Authenticate and get account token
Charges History/api/charges_history/get_charges_history_list/Retrieve transaction history
CDRs Export/api/cdrs_exportGenerate a CDR report for a selected date range. The report is delivered to the account registered email address as an Excel file inside a ZIP attachment.
Get Country ListDisabled in current referenceUse numeric country IDs provided in the current API reference example
DID Available List/customer/did_crud/Browse available numbers by country
DID Assign/customer/did_management/Purchase and assign a number
DID Purchased List/customer/did_crud/List all numbers on your account
DID Release/customer/did_management/Release a number from your account
DID Forward Setting/customer/did_management/Configure call forwarding for a number
SMS Config Add/api/smsCreate SMS, email, or webhook forwarding configuration
SMS Config Update/api/smsUpdate SMS, email, or webhook forwarding configuration
SMS Config Delete/api/smsDelete SMS forwarding config
Get SMS Config/api/smsGet SMS config for a specific DID
SMS Config List/api/smsList all SMS configs on account
Outbound SMS Sendhttps://api.pbxme.com/astppsend-smsSend outbound SMS via separate HTTP GET API
Inbound SMS → Webhook/api/sms or account HTTP portalConfigure inbound SMS forwarding to an HTTP endpoint using webhook_url

More API Guides

Ready to Call the API?

Create an account and build against the documented API calls and separately identified operational endpoints above.

    Sales, click to chat