E911 Addresses V1

E911 Address operations

List all E911 addresses

Returns a list of your E911 addresses.

Request
query Parameters
page
integer
Default: 1

Page number of results to load

per_page
integer <= 1000
Default: 100

Number of results per page

Responses
200

E911 Addresses response

Response Schema: application/json
Array
id
required
string
first_name
required
string
last_name
required
string
business_name
required
string
line_1
required
string
line_2
required
string
city
required
string
state
required
string
postal_code
required
string
401

Unauthorized

get/origination/e911_addresses
Request samples 
Response samples 
application/json
[
  • {
    • "id": "string",
    • "first_name": "string",
    • "last_name": "string",
    • "business_name": "string",
    • "line_1": "string",
    • "line_2": "string",
    • "city": "string",
    • "state": "string",
    • "postal_code": "string"
    }
]
Create an E911 address
IMPORTANT: In order to use E911 services, Terms of Service must first be accepted through
the Telnyx portal.


Creating an E911 Address requires the address fields to exactly match E911 Service records.
All capital letters, and no punctuation is generally sufficient. For example, '123 Main St.' would
be entered as '123 MAIN ST' in order to be valid. If there is not an exact match, a normalized
address will be returned for your confirmation, and the status field will indicate so.


If the address submitted is invalid, then the endpoint will return an error and a corrected address. The endpoint must be called again with the corrected address.


NOTE: Enabling E911 for a number is done via PUT/origination/numbers/{id}/e911_settings


Request 
Request Body schema: application/json
required
E911 Address to add


first_name
string
Required if business name not given


 
last_name
string
Required if business name not given


 
business_name
string
Required if personal name not given


 
line_1
required
string
Address first line


 
line_2
string
Address second line


 
city
required
string
 
state
required
string
 
postal_code
required
string
 
Responses 
200
E911 Address created response


Response Schema: application/json
id
required
string
 
first_name
required
string
 
last_name
required
string
 
business_name
required
string
 
line_1
required
string
 
line_2
required
string
 
city
required
string
 
state
required
string
 
postal_code
required
string
 
status
required
string
 Default:  "success"
 
400
Bad request


401
Unauthorized


post/origination/e911_addresses
Request samples 
application/json
{
  • "first_name": "John",
  • "last_name": "Doe",
  • "business_name": "MyCo, Inc",
  • "line_1": "123 Main St",
  • "line_2": "Apt 1",
  • "city": "Chicago",
  • "state": "IL",
  • "postal_code": "60654"
}
Response samples 
application/json
{
  • "id": "string",
  • "first_name": "string",
  • "last_name": "string",
  • "business_name": "string",
  • "line_1": "string",
  • "line_2": "string",
  • "city": "string",
  • "state": "string",
  • "postal_code": "string",
  • "status": "success"
}
Retrieve an E911 address
Retrieves the details of an existing E911 address.


Request 
path Parameters
id
required
string
ID of E911 Address to retrieve


 
Responses 
200
E911 Address record response


Response Schema: application/json
id
required
string
 
first_name
required
string
 
last_name
required
string
 
business_name
required
string
 
line_1
required
string
 
line_2
required
string
 
city
required
string
 
state
required
string
 
postal_code
required
string
 
401
Unauthorized


404
Resource not found


get/origination/e911_addresses/{id}
Request samples 
Response samples 
application/json
{
  • "id": "string",
  • "first_name": "string",
  • "last_name": "string",
  • "business_name": "string",
  • "line_1": "string",
  • "line_2": "string",
  • "city": "string",
  • "state": "string",
  • "postal_code": "string"
}
Delete an E911 address
Permanently deletes an E911 address.


Request 
path Parameters
id
required
string
ID of E911 Address to delete


 
Responses 
200
E911 Address deleted response


Response Schema: application/json
success
required
boolean
 
message
required
string
 
404
Resource not found


delete/origination/e911_addresses/{id}
Request samples 
Response samples 
application/json
{
  • "success": true,
  • "message": "string"
}