Update E911

Update the E911 service status for a list of numbers.

Note: E911 addresses require very strict matching. It is recommended to validate the service address before calling any of the E911 APIs.

Endpoint and Methods

PUT: /_rest/v3/my/did/e911

Parameters

Header

  • Accept: application/json
  • Authorization: xxxxxxxxxxxxxxxxx
  • Content-Type: application/json
Field Type Description
Accept STRING application/json
Authorization STRING Authorization token (for more information, see Atmosphere® API Authentication)
Content-Type STRING application/json

Path

Field Type Description
address1 STRING The first line of the service address.
address2 (optional) STRING The second line of the service address.
city STRING The city of the service address.
locationName STRING A name for the service location.
numbers ARRAY

An array of numbers to provide E911 service for.

Each item is in the following form:

{

"countryCode": "1",

"number": "1112223456"

}

Email (optional) STRING An e-mail address to notify about changes in the order’s status.
Notes (optional) STRING Notes regarding the fulfilment of the order.
referenceID (optional) STRING A non-empty string indicating your reference ID or code.
serviceBusiness STRING The company ordering E911 service.
serviceUser STRING The person ordering E911 service.
serviceUserTitle STRING The title of the person ordering E911 service.
state STRING Two-digit state of the service address.
zip STRING The zip code of the service address.

Request

Copy
{

    "serviceBusiness": "ABC Printing",

    "serviceUser": "Ted Dillon",

    "serviceUserTitle": "VP IT",

    "locationName": "AZ Fastening",

    "address1": "8050 NW 64TH ST",

    "city": "MIAMI",

    "state": "FL",

    "zip": "33166",

    "numbers": [

        {

            "countryCode": "1",

            "number": "2125550001"

        },

        {

            "countryCode": "1",

            "number": "2125550002"

        }

    ]

}

Response Example and Schema

Success 200

Field Type Description
order OBJECT A complex object identifying batch-specific and number provisioning details.
orderID INTEGER The overall ID associated with this order.
batches ARRAY An array of “batch” objects with associated number provisioning details.
batchID INTEGER The ID associated with this portion of the order (batch).
numbers ARRAY An array of objects specifying the numbers and provisioning attributes associated with this particular batch.
callerID (optional) STRING

The provisioning status of caller ID lookup service, if ordered/applicable (see network for value descriptions).

Allowed values: PENDING, PROVISIONED, QUEUED

Cnam (optional) STRING

The provisioning status of Caller ID Registration (CNAM) service, if ordered/applicable (see network for value descriptions).

Allowed values: PENDING, PROVISIONED, QUEUED

countryCode NUMERIC The number’s country code.
directoryListing (optional) STRING

The provisioning status of Directory Listing service, if ordered/applicable (see network for value descriptions).

Allowed values: PENDING, PROVISIONED, QUEUED

e164 NUMERIC The e.164 representation of the number.
E911 (optional) STRING

The provisioning status of 911 service, if ordered/applicable (see network for value descriptions).

Allowed values: PENDING, PROVISIONED, QUEUED

e911Address (optional) OBJECT If the order is adding or changing 911 service, this is the associated address.
name STRING The name/label of the 911 registration address.
address1 STRING The first line of the 911 registration address.
address2 STRING The second line of the 911 registration address.
city STRING The city of the 911 registration address.
state STRING The state of the 911 registration address.
network STRING

The number’s provisioning status.

Allowed values: PENDING, PROVISIONED, QUEUED

  • PENDING: Our services and systems have begun the necessary work to provide this service.
  • PROVISIONED: Our services and systems have completed the necessary work and the service is currently active, unless altered by a later order.
  • QUEUED: Our services and systems are aware that work needs to occur, but the work has not been started yet.
number OBJECT The number.

Success Response

Copy
HTTP/1.1 200 OK

{

  "orderID": 12345,

  "batches": [

    {

      "batchID": 23456,

      "numbers": [

        {

          "callerID": null,

          "cnam": null,

          "countryCode": "1",

          "directoryListing": null,

          "e164": "+12125550001",

          "e911": "QUEUED",

          "e911Address": "e911Address": {

            "location": "AZ Fastening",

            "address1": "8050 NW 64TH ST",

            "address2": null,

            "city": "MIAMI",

            "state": "FL",

            "zip": "33166"

          },

          "network": null,

          "number": "2125550001"

        },

        {

          "callerID": null,

          "cnam": null,

          "countryCode": "1",

          "directoryListing": null,

          "e164": "+12125550002",

          "e911": "QUEUED",

          "e911Address": "e911Address": {

            "location": "AZ Fastening",

            "address1": "8050 NW 64TH ST",

            "address2": null,

            "city": "MIAMI",

            "state": "FL",

            "zip": "33166"

          },

          "network": null,

          "number": "2125550002"

        }

      ]

    }

  ]

}

Error

Name Type Description
code INTEGER Error code
error STRING Error description

Code 401 Response

Copy
HTTP/1.1 401 Unauthorized

{

    "code": 401,

    "error": "Unauthorized"

}

 

Copy
HTTP/1.1 401 Unauthorized

{

    "code": 401,

    "error": "Session Expired"

}

Code 404 Response

Copy
HTTP/1.1 404 Not Found

{

    "code": 404,

    "error": "Location not recognized."

}

 

Copy
HTTP/1.1 404 Not Found

{

    "code": 404,

    "error": "Validation does not match: %s."

}

Code 406 Response

Copy
HTTP/1.1 406 Not Acceptable

{

    "code": 406,

    "error": "Not Acceptable"

}

Code 409 Response

Copy
HTTP/1.1 409 Conflict

{

    "code": 409,

    "error": "One or more numbers are not assigned to this account."

}

 

Copy
HTTP/1.1 409 Conflict

{

    "code": 409,

    "error": "One or more numbers are part of an active order: %d"

}

 

Copy
HTTP/1.1 409 Conflict

{

    "code": 409,

    "error": "One or more numbers do not have service: %s"

}

 

Copy
HTTP/1.1 409 Conflict

{

    "code": 409,

    "error": "One or more numbers are already pending disconnect: %s"

}

Code 422 Response

Copy
HTTP/1.1 422 Unprocessable Entity

{

    "code": 422,

    "error": "The '%s' parameter is required."

}

 

Copy
HTTP/1.1 422 Unprocessable Entity

{

    "code": 422,

    "error": "The '%s' parameter must be scalar."

}

 

Copy
HTTP/1.1 422 Unprocessable Entity

{

    "code": 422,

    "error": "The '%s' parameter must be formatted as a(n) string."

}

 

Copy
HTTP/1.1 422 Unprocessable Entity

{

    "code": 422,

    "error": "The '%' parameter is required for each Number object."

}

 

Copy
HTTP/1.1 422 Unprocessable Entity

{

    "code": 422,

    "error": "The 'countryCode' parameter must match one of the following values: 1"

}

 

Copy
HTTP/1.1 422 Unprocessable Entity

{

    "code": 422,

    "error": "The 'number' parameter must be 10 numeric digits."

}