Line Test API v2 is now available giving access to enriched ONT information

By
admin
date Created with Sketch.
January 29, 2020

With the release of Line Test API v2.0, Line Test API v1.0 is now deprecated.

Line Test API v2 is now available giving access to enriched ONT information.

 

What's happening

With the release of Line Test API v2.0, we are deprecating Line Test API v1.0. This means that onboarding for v1.0 will no longer be available and RSPs taking up the Line Test API will be onboarded to v2.0. Any future development will only go into v2.0.

Line Test API v1.0 will remain available for use and will be supported until it is officially decommissioned in 12 months (unless it is no longer in use, in which case we will provide 20 days’ notice before decommissioning).

If you are currently using v1.0 then it should only require a few small changes to adapt to v2.0 for the same functionality. 

 

Migrating from Line Test API v1.0 to v2.0

Apart from different end points between Line Test API v1 and v2, there are very small payload changes as noted in the table below:

Line Test API v1 payload Line Test API v2 payload
"ont": {
      "id": "NPE-POLT05:1-1-4-8-3",
      "ports": "4",
      "tlc": "101593704",
      "type": "4+2 Standard",
      "ontSerialNumber": "ALCL45781245"
}
 "ont": {
      "id": "NPE-POLT05:1-1-4-8-3",
      "ports": "4",
      "ataPorts": "1",
      "mode": "Standard"
      "model": "G-140W-C",
      "tlc": "101593704",
      "type": "Type 300",
      "ontSerialNumber": "ALCLB30F63A1"
}


Note: 

  1. Above text is the only part of the payload that's changing in v2, rest of the payload remains the same
  2. Possible values for ports can be 1 or 4 (in v1, it used to be hardcoded to 4 at all times)
  3. Possible values for ataPorts can be 1 or 2
  4. Possible values for model can be G-140W-C, G-240G-P, I-240G-R, G-010S-P or G-010S-A
  5. Possible values for type can be Type 100, Type 200, Type 300 or SFP

 

Next steps

Please contact API@Chorus.co.nz for any support, questions or queries on APIs including migration to v2.0. Alternatively, ask your Service Delivery Manager to arrange a meeting with our API team to go through the change.