PortInAccepted
Fired when the losing carrier has accepted a port-in request.
PortInAccepted
Fired when the losing carrier accepts the port-in. From this event on, executionDate is the date the carrier confirmed, which may differ from the date you requested.
Payload
{
"id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"eventType": "PortInAccepted",
"timestamp": "2026-03-25T14:30:00.000Z",
"organizationId": "b5e2d7f3-a1c4-4e89-9f6b-3d8a7c5e1024",
"data": {
"portInId": "d4e5f6a7-b8c9-0123-d456-789012345678",
"numberId": "f7a8b9c0-d1e2-3456-f789-012345678901",
"phoneNumber": "+4512345678",
"countryCode": "DK",
"state": "ACCEPTED",
"executionDate": "2026-04-01",
"failureDetails": null
}
}Payload fields
Every port-in event carries these fields.
| Field | Type | Description |
|---|---|---|
portInId | string | UUID of the port-in request |
numberId | string | UUID of the number being ported |
phoneNumber | string | Phone number in E.164 format |
countryCode | string | ISO 3166-1 alpha-2 country code |
state | string | The port-in state that triggered the event |
executionDate | string | null | The porting date (YYYY-MM-DD): the date you requested until the carrier accepts, then the date it confirmed |
failureDetails | object | null | Why a rejected or failed port-in ended that way; null otherwise |
failureDetails holds a code, a text to show your customer and, when the failure could be classified, a reason and the field the carrier objected to. reason and field are left out, never null, when there is nothing to say. See the port-in guide for every failure code and reason, and what to do about each.