This page describes the technical aspect of the Datafeed Service where

[numberDesc]

porting events are made available via FTP or SFTP.

Upon initial service activation, a client will be given access to an FTP or SFTP host. The datafeed server will contain an initial snapshot file containing the state of all

[numberDesc]

ports at a given point in time. This is used to prime a client's internal systems.

From this point onwards a daily or weekly delta file will be made available containing all subsequent porting events. The delta files are available for download from 3am each day for the daily service or from 3am each Sunday for the weekly service.
Typically a client schedules a job to automatically get (in binary mode) the latest delta file on a daily or weekly basis.

File naming convention

There are 2 types of files, the initial snapshot file (one-off) and the ongoing delta files. The naming conventions for these are as follows:

  • [numberType]

    Initial.txt.gz

  • [numberType]

    DY[DDMMYY].txt.gz (daily) or

    [numberType]

    WK[DDMMYY].txt.gz (weekly)

So as an example a daily delta file on the 28 Jan 2022 would be

[numberType]

DY280122.txt.gz

The gz suffix is standard zip format.

File content

The initial and delta files contain rows in ACSII format. Each row is a porting event that contains exactly 3 fields each delimited by a comma ",". These fields are an Action Indicator, a

[numberDesc]

and a CAC.

The Action Indicator values are:
  • A = Add, means a newly ported number (only A's will appear in the initial snapshot file)
  • C = Change, means a number that's been ported in the past and has now been ported again
  • D = Delete, means a number has been returned to the original allocated carrier

Here's a

[numberFile]

delta file (unzipped for convenience) for

[numberType]

.

Authentication

FTP authentication is done via username and password, for SFTP it's username and SSH key.