Getting started

Keys

Using the API requires a key for authentication. Each key is linked with one staff user; access to the data will be linked to the same access level of that staff member.

  • To obtain or create new keys navigate to Management > Api
  • Note: A key is like combined username + password to your RPM subscription keep it secure.

API Access URL And Endpoints

All the API calls are done through one web service, available at the following URL:

Cube and Lighthouse:

https://secure.cubedms.com/rpm/api2.svc/<api-endpoint>

RPM Telco:

https://secure.rpmtelco.com/rpm/api2.svc/<api-endpoint>

How to Construct a Request to our API

All the requests to the API are done using JSON formatting and the HTTP POST method is required.

Every request sent to the API requires the call parameters to be provided in JSON format. Regardless of what endpoint you are trying to request, you need to provide the API key in the HTTP request header in the following way:

POST http://localhost/rpm/Api2.svc/<endpoint> HTTP/1.1
RpmApiKey: ffffffff-ffff-ffff-ffff-ffffffffffff

{
    ... other data
}

Any request with a missing API Key will respond with an error:

{
  "Result": {
    "Error": "Valid key required"
  }
}

Invalid keys produce errors too:

{
  "Result": {
    "Error": "Key not found.  A valid \"Key\" must appear as the first input data item."
  }
}

Example Request:

POST http://rpmtelco.com/rpm/Api2.svc/Info HTTP/1.1
RpmApiKey: 12345678-1234-1234-1234-123abc

{}

Response

{   
  "InfoResult":
    {     
      "Subscriber":"Test Inc.",
      "RPM":"AGENT",
      "Role":"Executive",
      "User":"johnsmith"   
    } 
}
%d bloggers like this: