Update Emergency Calling Service

This example shows how to update an existing Emergency Calling Service by submitting a new emergency verification in Existing Calling Service.

Use this flow when an Emergency Calling Service already exists and its registered emergency address must be changed without creating a new service.

This update flow is typically used in these situations:

  • the existing Emergency Calling Service is in changes_required because the previous emergency verification was rejected and the address must be corrected and resubmitted

  • the existing Emergency Calling Service is already active, but the registered emergency address needs to be changed to a new one

  • the existing Emergency Calling Service is still in new, which means the service already exists but has not become active yet, so the address can still be replaced before activation finishes

To update an existing Emergency Calling Service, follow these steps:

Note

Adding or removing DIDs from an existing Emergency Calling Service is handled through the DID resource, not through emergency verification creation.


Before you begin

  • A DIDWW API key is required to authenticate the requests shown in this guide. Make sure you have an API key ready before starting the flow.

  • You must already have an existing Emergency Calling Service to update. If you do not have one yet, first follow Register Emergency Calling Service.


Step 1: Review the Existing Emergency Calling Service

Before the address can be updated, the existing Emergency Calling Service has to be identified and checked. This is what tells your application whether that specific service can accept an address change right now and which service rules the replacement address still has to follow.

Retrieve the existing Emergency Calling Service so you can confirm:

  • the existing Emergency Calling Service id

  • the current Emergency Calling Service status

  • the linked emergency_requirement that still defines the allowed address scope

  • the currently linked emergency verification and DIDs

  • the country and DID Group type assigned to that Emergency Calling Service

This step matters because the existing service defines the update context. It shows which service is being updated, whether the service is currently allowed to accept an address change, and which country and DID Group type rules the new address still has to satisfy.

Address changes are allowed only when the Emergency Calling Service is in one of these statuses:

  • new

  • changes_required

  • active

The update submission request fails with 422 if the Emergency Calling Service is in:

  • pending_update

  • in_process

  • canceled

From this response, save:

  • emergency_calling_service.id for Step 4

  • emergency_verification.id for Step 2, so you can retrieve the current address linked to the service

From the linked emergency_requirement, review the address rules that still apply to this service, especially address_area_level and address_mandatory_fields.

For more information, see Get Emergency Calling Service endpoint documentation and the Emergency Calling Service object.

http

GET /v3/emergency_calling_services?filter%5Breference%5D=SHB-485120&include=country%2Cdid_group_type%2Cdids%2Cemergency_verification%2Cemergency_requirement HTTP/1.1
Host: api.didww.com
Api-Key: [API token]
Accept: application/vnd.api+json

curl

curl -i -X GET 'https://api.didww.com/v3/emergency_calling_services?filter%5Breference%5D=SHB-485120&include=country%2Cdid_group_type%2Cdids%2Cemergency_verification%2Cemergency_requirement' -H "Accept: application/vnd.api+json" -H "Api-Key: [API token]"

response

HTTP/1.1 200 OK
Content-Type: application/vnd.api+json

{
    "data": [
        {
            "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
            "type": "emergency_calling_services",
            "attributes": {
                "name": "E911 Service - New York Office",
                "reference": "SHB-485120",
                "status": "active",
                "activated_at": "2026-01-15T10:30:00.000Z",
                "canceled_at": null,
                "renew_date": "2026-07-15",
                "created_at": "2026-01-10T08:00:00.000Z"
            },
            "relationships": {
                "country": {
                    "data": {
                        "type": "countries",
                        "id": "72f22218-ab1f-4933-a74d-a6467f3f6cb0"
                    }
                },
                "did_group_type": {
                    "data": {
                        "type": "did_group_types",
                        "id": "994ea201-4a4d-4b27-ac4b-b5916ac969a3"
                    }
                },
                "emergency_requirement": {
                    "data": {
                        "type": "emergency_requirements",
                        "id": "6da88c80-99ab-42b7-bd10-66dcf53ca278"
                    }
                },
                "emergency_verification": {
                    "data": {
                        "type": "emergency_verifications",
                        "id": "d4e5f6a7-b8c9-0123-def0-123456789012"
                    }
                },
                "dids": {
                    "data": [
                        {
                            "type": "dids",
                            "id": "cc4c423f-68b5-4e1a-878c-2328eb24f3fa"
                        }
                    ]
                }
            },
            "meta": {
                "setup_price": "0.00",
                "monthly_price": "2.50"
            }
        }
    ],
    "included": [
        {
            "id": "6da88c80-99ab-42b7-bd10-66dcf53ca278",
            "type": "emergency_requirements",
            "attributes": {
                "identity_type": "any",
                "address_area_level": "country",
                "personal_area_level": "world_wide",
                "business_area_level": "world_wide",
                "address_mandatory_fields": [],
                "personal_mandatory_fields": [],
                "business_mandatory_fields": [],
                "estimate_setup_time": "15-17 days",
                "requirement_restriction_message": "United States Local DID Emergency calling requirements:\r\n\r\nFor personal identity verification:\r\n* Name, last name\r\n* Contact phone number\r\n\r\nFor business identity verification:\r\n* Name, last name\r\n* Contact phone number\r\n* Company name\r\n\r\nFor address verification:\r\n* Address in United States (state, city, street, street number, apartment or suite information, zip code)\r\n"
            },
            "meta": {
                "setup_price": "0.00",
                "monthly_price": "10.20"
            }
        }
    ],
    "meta": {
        "api_version": "2026-04-16"
    }
}

Important

When you update an active service, the service transitions to pending_update while the new verification is reviewed, but emergency routing remains enabled until the new verification is approved or rejected.

During that review period, the existing Emergency Calling Service continues to be used with the current address. The replacement address only takes effect after the update verification is approved and the service returns to active.


Step 2: Prepare the Replacement Address

The Emergency Calling Service update flow does not change the registered service address directly. Instead, it prepares the address record that will be submitted for review in Step 3.

At this point, your application has to decide whether the current address can still be edited or whether a new address must be created instead.

  • edit the current address only if that address has not yet been approved or used in emergency verification

  • create a new address if the current address has already been approved or used, because that address should no longer be modified in place

In both cases, the replacement address still has to satisfy the same emergency_requirement already linked to the existing Emergency Calling Service. Review that requirement from Step 1, especially:

  • address_area_level

  • address_mandatory_fields

For more information, see Create Addresses endpoint documentation and the Address object.

Use this path only when the current address has not yet been approved or used in emergency verification.

This path exists for the case where the address record can still be corrected in place. In that situation, your application does not need to create another address record. It only needs to identify the existing address, update its address fields, and then submit that corrected address in Step 3.

First retrieve the current emergency verification to get the address.id currently linked to the Emergency Calling Service. That lookup is needed because the update flow starts from the Emergency Calling Service and emergency verification, not from a previously known address ID.

http

GET /v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012?include=address HTTP/1.1
Host: api.didww.com
Api-Key: [API token]
Accept: application/vnd.api+json

curl

curl -i -X GET 'https://api.didww.com/v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012?include=address' -H "Accept: application/vnd.api+json" -H "Api-Key: [API token]"

response

HTTP/1.1 200 OK
Content-Type: application/vnd.api+json

{
  "data": {
    "id": "d4e5f6a7-b8c9-0123-def0-123456789012",
    "type": "emergency_verifications",
    "attributes": {
      "reference": "SHB-998877",
      "status": "approved",
      "reject_reasons": [],
      "reject_comment": null,
      "callback_url": "https://example.com/callbacks/emergency",
      "callback_method": "post",
      "created_at": "2026-03-23T09:15:00.000Z",
      "external_reference_id": null
    },
    "relationships": {
      "address": {
        "data": {
          "type": "addresses",
          "id": "46e129f1-deaa-44db-8915-2646de4d4c70"
        }
      },
      "emergency_calling_service": {
        "data": {
          "type": "emergency_calling_services",
          "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
        }
      }
    }
  },
  "included": [
    {
      "id": "46e129f1-deaa-44db-8915-2646de4d4c70",
      "type": "addresses",
      "attributes": {
        "address": "10 Old Address Street",
        "city_name": "New York",
        "postal_code": "10001",
        "description": "Current emergency address",
        "created_at": "2026-01-10T08:55:00.000Z",
        "verified": false,
        "external_reference_id": null
      }
    }
  ],
  "meta": {
    "api_version": "2026-04-16"
  }
}

Then update that address with the corrected address data that should replace the current Emergency Calling Service address if the review is approved. This keeps the flow on the same address record and prepares the exact address version that the API will review in Step 3.

http

PATCH /v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70 HTTP/1.1
Host: api.didww.com
Api-Key: [API token]
Content-Type: application/vnd.api+json
Accept: application/vnd.api+json

{
  "data": {
    "id": "46e129f1-deaa-44db-8915-2646de4d4c70",
    "type": "addresses",
    "attributes": {
      "address": "20 Example Street",
      "city_name": "New York",
      "postal_code": "10002",
      "description": "Updated emergency address"
    }
  }
}

curl

curl -i -X PATCH https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70 -H "Accept: application/vnd.api+json" -H "Api-Key: [API token]" -H "Content-Type: application/vnd.api+json" --data-raw '{"data": {"attributes": {"address": "20 Example Street", "city_name": "New York", "description": "Updated emergency address", "postal_code": "10002"}, "id": "46e129f1-deaa-44db-8915-2646de4d4c70", "type": "addresses"}}'

response

HTTP/1.1 200 OK
Content-Type: application/vnd.api+json

{
  "data": {
    "id": "46e129f1-deaa-44db-8915-2646de4d4c70",
    "type": "addresses",
    "attributes": {
      "address": "20 Example Street",
      "city_name": "New York",
      "postal_code": "10002",
      "description": "Updated emergency address",
      "created_at": "2026-01-10T08:55:00.000Z",
      "verified": false,
      "external_reference_id": null
    },
    "relationships": {
      "identity": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/relationships/identity",
          "related": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/identity"
        }
      },
      "country": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/relationships/country",
          "related": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/country"
        }
      },
      "proofs": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/relationships/proofs",
          "related": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/proofs"
        }
      },
      "area": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/relationships/area",
          "related": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/area"
        }
      },
      "city": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/relationships/city",
          "related": "https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70/city"
        }
      }
    }
  },
  "meta": {
    "api_version": "2026-04-16"
  }
}

From this step, save address.id for Step 3.

Use this path when the current address has already been approved or used in emergency verification and should no longer be changed in place.

This path exists for the case where the current address record should be left unchanged and a replacement address must be prepared separately. That usually means the existing address already has compliance history, so the safer and correct update path is to create a new address record and submit that new record in Step 3.

First retrieve the current emergency verification to get the current address.id. That identifies the address currently used by the Emergency Calling Service and gives your application a starting point for finding the linked identity and country needed for the new address.

http

GET /v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012?include=address HTTP/1.1
Host: api.didww.com
Api-Key: [API token]
Accept: application/vnd.api+json

curl

curl -i -X GET 'https://api.didww.com/v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012?include=address' -H "Accept: application/vnd.api+json" -H "Api-Key: [API token]"

response

HTTP/1.1 200 OK
Content-Type: application/vnd.api+json

{
  "data": {
    "id": "d4e5f6a7-b8c9-0123-def0-123456789012",
    "type": "emergency_verifications",
    "attributes": {
      "reference": "SHB-998877",
      "status": "approved",
      "reject_reasons": [],
      "reject_comment": null,
      "callback_url": "https://example.com/callbacks/emergency",
      "callback_method": "post",
      "created_at": "2026-03-23T09:15:00.000Z",
      "external_reference_id": null
    },
    "relationships": {
      "address": {
        "data": {
          "type": "addresses",
          "id": "46e129f1-deaa-44db-8915-2646de4d4c70"
        }
      },
      "emergency_calling_service": {
        "data": {
          "type": "emergency_calling_services",
          "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
        }
      }
    }
  },
  "included": [
    {
      "id": "46e129f1-deaa-44db-8915-2646de4d4c70",
      "type": "addresses",
      "attributes": {
        "address": "10 Old Address Street",
        "city_name": "New York",
        "postal_code": "10001",
        "description": "Current emergency address",
        "created_at": "2026-01-10T08:55:00.000Z",
        "verified": false,
        "external_reference_id": null
      }
    }
  ],
  "meta": {
    "api_version": "2026-04-16"
  }
}

Then retrieve that address to get the linked identity.id and country.id required for the create request. Those IDs are needed because the new address still has to stay linked to the correct identity and country context already used by the existing Emergency Calling Service.

http

GET /v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70?include=identity%2Ccountry HTTP/1.1
Host: api.didww.com
Api-Key: [API token]
Accept: application/vnd.api+json

curl

curl -i -X GET 'https://api.didww.com/v3/addresses/46e129f1-deaa-44db-8915-2646de4d4c70?include=identity%2Ccountry' -H "Accept: application/vnd.api+json" -H "Api-Key: [API token]"

response

HTTP/1.1 200 OK
Content-Type: application/vnd.api+json

{
  "data": {
    "id": "46e129f1-deaa-44db-8915-2646de4d4c70",
    "type": "addresses",
    "attributes": {
      "address": "10 Old Address Street",
      "city_name": "New York",
      "postal_code": "10001",
      "description": "Current emergency address",
      "created_at": "2026-01-10T08:55:00.000Z",
      "verified": false,
      "external_reference_id": null
    },
    "relationships": {
      "identity": {
        "data": {
          "type": "identities",
          "id": "beca16fb-0385-462f-9e2c-0d1918f6c8af"
        }
      },
      "country": {
        "data": {
          "type": "countries",
          "id": "72f22218-ab1f-4933-a74d-a6467f3f6cb0"
        }
      }
    }
  },
  "included": [
    {
      "id": "beca16fb-0385-462f-9e2c-0d1918f6c8af",
      "type": "identities",
      "attributes": {
        "identity_type": "business",
        "company_name": "Example Company Ltd",
        "first_name": "John",
        "last_name": "Smith",
        "phone_number": "15551234567",
        "created_at": "2026-01-09T07:30:12.546Z",
        "verified": true,
        "external_reference_id": null,
        "contact_email": null
      }
    },
    {
      "id": "72f22218-ab1f-4933-a74d-a6467f3f6cb0",
      "type": "countries",
      "attributes": {
        "name": "United States",
        "prefix": "1",
        "iso": "US"
      }
    }
  ],
  "meta": {
    "api_version": "2026-04-16"
  }
}

After that, create the new replacement address that will be submitted in Step 3. This prepares a separate address record for review without changing the existing address that is already tied to the current Emergency Calling Service state.

If the current Emergency Calling Service is already active, submit a different address record in the update request. Do not resubmit the same address record already used by that service.

http

POST /v3/addresses HTTP/1.1
Host: api.didww.com
Api-Key: [API token]
Content-Type: application/vnd.api+json
Accept: application/vnd.api+json

{
  "data": {
    "type": "addresses",
    "attributes": {
      "address": "20 Example Street",
      "city_name": "New York",
      "postal_code": "10002",
      "description": "Updated emergency address"
    },
    "relationships": {
      "identity": {
        "data": {
          "type": "identities",
          "id": "beca16fb-0385-462f-9e2c-0d1918f6c8af"
        }
      },
      "country": {
        "data": {
          "type": "countries",
          "id": "72f22218-ab1f-4933-a74d-a6467f3f6cb0"
        }
      }
    }
  }
}

curl

curl -i -X POST https://api.didww.com/v3/addresses -H "Accept: application/vnd.api+json" -H "Api-Key: [API token]" -H "Content-Type: application/vnd.api+json" --data-raw '{"data": {"attributes": {"address": "20 Example Street", "city_name": "New York", "description": "Updated emergency address", "postal_code": "10002"}, "relationships": {"country": {"data": {"id": "72f22218-ab1f-4933-a74d-a6467f3f6cb0", "type": "countries"}}, "identity": {"data": {"id": "beca16fb-0385-462f-9e2c-0d1918f6c8af", "type": "identities"}}}, "type": "addresses"}}'

response

HTTP/1.1 201 Created
Content-Type: application/vnd.api+json

{
  "data": {
    "id": "f13240d5-d3cc-4c05-a529-fb63a0027118",
    "type": "addresses",
    "attributes": {
      "address": "20 Example Street",
      "city_name": "New York",
      "postal_code": "10002",
      "description": "Updated emergency address",
      "created_at": "2026-03-23T09:02:11.000Z",
      "verified": false,
      "external_reference_id": null
    },
    "relationships": {
      "identity": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/relationships/identity",
          "related": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/identity"
        }
      },
      "country": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/relationships/country",
          "related": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/country"
        }
      },
      "proofs": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/relationships/proofs",
          "related": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/proofs"
        }
      },
      "area": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/relationships/area",
          "related": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/area"
        }
      },
      "city": {
        "links": {
          "self": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/relationships/city",
          "related": "https://api.didww.com/v3/addresses/f13240d5-d3cc-4c05-a529-fb63a0027118/city"
        }
      }
    }
  },
  "meta": {
    "api_version": "2026-04-16"
  }
}

From this step, save the new address.id for Step 3.


Step 3: Submit Emergency Verification in Existing Calling Service

The existing Emergency Calling Service is updated by creating a new emergency verification in Existing Calling Service. This is the request that starts the review of the replacement address for that already existing service.

Submit a new emergency verification with address and emergency_calling_service.

This step is what actually starts the Emergency Calling Service update review. The request tells the API which existing Emergency Calling Service should be updated and which new address should replace the current service address if the review is approved.

While submitting the update, you can still receive an error if the replacement address is linked to the wrong identity, does not satisfy the Emergency Calling Service requirement, or if the Emergency Calling Service is currently in a status that does not allow updates. Those checks happen at submission time because the API must confirm that the replacement address is valid for the specific existing service being changed.

Note

A callback_url and callback_method can be configured for emergency verifications to receive HTTP callbacks when the verification status changes.
Callback events are sent when the verification is approved or rejected. The payload includes the verification ID, resource type (emergency_verifications), the current status, and a rejection reason when applicable.

See Callback configuration for more information.

For more information, see Create Emergency Verification.

http

POST /v3/emergency_verifications HTTP/1.1
Host: api.didww.com
Api-Key: [API token]
Content-Type: application/vnd.api+json
Accept: application/vnd.api+json

{
  "data": {
    "type": "emergency_verifications",
    "attributes": {
      "callback_url": "https://example.com/callbacks/emergency",
      "callback_method": "post"
    },
    "relationships": {
      "address": {
        "data": {
          "type": "addresses",
          "id": "f13240d5-d3cc-4c05-a529-fb63a0027118"
        }
      },
      "emergency_calling_service": {
        "data": {
          "type": "emergency_calling_services",
          "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
        }
      }
    }
  }
}

curl

curl -i -X POST https://api.didww.com/v3/emergency_verifications -H "Accept: application/vnd.api+json" -H "Api-Key: [API token]" -H "Content-Type: application/vnd.api+json" --data-raw '{"data": {"attributes": {"callback_method": "post", "callback_url": "https://example.com/callbacks/emergency"}, "relationships": {"address": {"data": {"id": "f13240d5-d3cc-4c05-a529-fb63a0027118", "type": "addresses"}}, "emergency_calling_service": {"data": {"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "type": "emergency_calling_services"}}}, "type": "emergency_verifications"}}'

response

HTTP/1.1 201 Created
Content-Type: application/vnd.api+json

{
  "data": {
    "id": "d4e5f6a7-b8c9-0123-def0-123456789012",
    "type": "emergency_verifications",
    "attributes": {
      "reference": "SHB-998877",
      "status": "pending",
      "reject_reasons": [],
      "reject_comment": null,
      "callback_url": "https://example.com/callbacks/emergency",
      "callback_method": "post",
      "created_at": "2026-03-23T09:15:00.000Z",
      "external_reference_id": null
    },
    "relationships": {
      "address": {
        "data": {
          "type": "addresses",
          "id": "f13240d5-d3cc-4c05-a529-fb63a0027118"
        }
      },
      "emergency_calling_service": {
        "data": {
          "type": "emergency_calling_services",
          "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
        }
      },
      "dids": {
        "data": []
      }
    }
  },
  "meta": {
    "api_version": "2026-04-16"
  }
}

Step 4: Track the Pending Update Until Activation

The update is not applied immediately after submission. It is reviewed asynchronously, so your application needs to track both the new emergency verification and the existing Emergency Calling Service until the review is finished and the service returns to its usable state.

After the update request is submitted:

  1. the new emergency verification status becomes pending

  2. the existing Emergency Calling Service status becomes pending_update

  3. once the update verification is approved, the Emergency Calling Service becomes active again with the updated address

Use these endpoints to track the change:

Get emergency verification

Use the emergency verification resource first to see whether the address update was approved or rejected.

http

GET /v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012?include=emergency_calling_service HTTP/1.1
Host: api.didww.com
Api-Key: [API token]
Accept: application/vnd.api+json

curl

curl -i -X GET 'https://api.didww.com/v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012?include=emergency_calling_service' -H "Accept: application/vnd.api+json" -H "Api-Key: [API token]"

response

HTTP/1.1 200 OK
Content-Type: application/vnd.api+json

{
  "data": {
    "id": "d4e5f6a7-b8c9-0123-def0-123456789012",
    "type": "emergency_verifications",
    "attributes": {
      "reference": "SHB-998877",
      "status": "approved",
      "reject_reasons": [],
      "reject_comment": null,
      "callback_url": "https://example.com/callbacks/emergency",
      "callback_method": "post",
      "created_at": "2026-03-23T09:15:00.000Z",
      "external_reference_id": null
    },
    "relationships": {
      "address": {
        "links": {
          "self": "https://api.didww.com/v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012/relationships/address",
          "related": "https://api.didww.com/v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012/address"
        }
      },
      "emergency_calling_service": {
        "data": {
          "type": "emergency_calling_services",
          "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
        },
        "links": {
          "self": "https://api.didww.com/v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012/relationships/emergency_calling_service",
          "related": "https://api.didww.com/v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012/emergency_calling_service"
        }
      },
      "dids": {
        "links": {
          "self": "https://api.didww.com/v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012/relationships/dids",
          "related": "https://api.didww.com/v3/emergency_verifications/d4e5f6a7-b8c9-0123-def0-123456789012/dids"
        }
      }
    }
  },
  "included": [
    {
      "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "type": "emergency_calling_services",
      "attributes": {
        "name": "E911 Service - New York Office",
        "reference": "SHB-485120",
        "status": "active",
        "activated_at": "2026-04-03T12:40:00.000Z",
        "canceled_at": null,
        "renew_date": "2026-07-15",
        "created_at": "2026-01-10T08:00:00.000Z"
      },
      "meta": {
        "setup_price": "0.00",
        "monthly_price": "2.50"
      }
    }
  ],
  "meta": {
    "api_version": "2026-04-16"
  }
}

Get the emergency calling service

After the emergency verification is approved, retrieve the Emergency Calling Service to confirm it has returned from pending_update to active with the updated address in effect.

Once the Emergency Calling Service status becomes active, the emergency-enabled DID can be assigned to an outbound trunk and used for outbound emergency traffic. For an example, see Create Outbound Trunk.

http

GET /v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890?include=emergency_verification%2Cdids HTTP/1.1
Host: api.didww.com
Api-Key: [API token]
Accept: application/vnd.api+json

curl

curl -i -X GET 'https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890?include=emergency_verification%2Cdids' -H "Accept: application/vnd.api+json" -H "Api-Key: [API token]"

response

HTTP/1.1 200 OK
Content-Type: application/vnd.api+json

{
  "data": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "type": "emergency_calling_services",
    "attributes": {
      "name": "E911 Service - New York Office",
      "reference": "SHB-485120",
      "status": "active",
      "activated_at": "2026-04-03T12:40:00.000Z",
      "canceled_at": null,
      "renew_date": "2026-07-15",
      "created_at": "2026-01-10T08:00:00.000Z"
    },
    "relationships": {
      "country": {
        "links": {
          "self": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/relationships/country",
          "related": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/country"
        }
      },
      "did_group_type": {
        "links": {
          "self": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/relationships/did_group_type",
          "related": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/did_group_type"
        }
      },
      "order": {
        "links": {
          "self": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/relationships/order",
          "related": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/order"
        }
      },
      "emergency_requirement": {
        "links": {
          "self": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/relationships/emergency_requirement",
          "related": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/emergency_requirement"
        }
      },
      "emergency_verification": {
        "data": {
          "type": "emergency_verifications",
          "id": "d4e5f6a7-b8c9-0123-def0-123456789012"
        },
        "links": {
          "self": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/relationships/emergency_verification",
          "related": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/emergency_verification"
        }
      },
      "dids": {
        "data": [
          {
            "type": "dids",
            "id": "cc4c423f-68b5-4e1a-878c-2328eb24f3fa"
          }
        ],
        "links": {
          "self": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/relationships/dids",
          "related": "https://api.didww.com/v3/emergency_calling_services/a1b2c3d4-e5f6-7890-abcd-ef1234567890/dids"
        }
      }
    },
    "meta": {
      "setup_price": "0.00",
      "monthly_price": "2.50"
    }
  },
  "included": [
    {
      "id": "d4e5f6a7-b8c9-0123-def0-123456789012",
      "type": "emergency_verifications",
      "attributes": {
        "reference": "SHB-998877",
        "status": "approved",
        "reject_reasons": [],
        "reject_comment": null,
        "callback_url": "https://example.com/callbacks/emergency",
        "callback_method": "post",
        "created_at": "2026-03-23T09:15:00.000Z",
        "external_reference_id": null
      }
    },
    {
      "id": "cc4c423f-68b5-4e1a-878c-2328eb24f3fa",
      "type": "dids",
      "attributes": {
        "number": "12125550100"
      }
    }
  ],
  "meta": {
    "api_version": "2026-04-16"
  }
}

Note

If the updated verification is rejected, review reject_reasons and reject_comment, correct the address data, and submit another POST /v3/emergency_verifications request in Existing Calling Service.