Manage Order API

(0 reviews)

Testing

Chorus NZ is committed to making integration with our APIs easy and robust and we are available to provide support for your development and testing.

For information on access and setup requirements for our emulation environment (EMMA) for testing the Fibre APIs, see Emulation Environment (EMMA).

On this page, you will find information on suggested test cases and test data.

Test cases

As with any software development, Chorus encourages you to test your application with both positive and negative scenarios. The test cases we've provided here are for your convenience, but are not intended to be comprehensive.

Some test cases may not apply to your use of the API. Please extend these cases with test cases that are specific to your business and use cases.

Comprehensive testing of your application should also include:

  • different types of requests
  • different types of data
  • handling errors and exceptions.

Learn more about our error codes

The following suggested test cases, are designed to assist you with creating. amending, and cancelling orders, as well as various GET requests for an order.

IDTest caseExpected resultEndpoints
FMO1Submit a Connect Primary order at a location for install.The API returns a 200 response and creates the order, which will be scheduled for the appointment requested./createOrder
FMO2Submit a Connect Primary order at an MDU/ROW location or where Fibre Availability Status is not Ready.The API returns a 200 response and creates the order, which will be manually processed by Chorus./createOrder
FMO3Submit a Connect Primary order at a location where an intact ONT is available to connect immediately.The API returns a 200 response and creates the order, which will be scheduled for the appointment requested./createOrder
FMO4Submit a Connect Additional ONT order at a location to install another ONT.The API returns a 200 response and creates the order, which will be scheduled for the appointment requested./createOrder
FMO5Submit a Transfer or Connect and Replace order at a location to replace a service.The API returns a 200 response and creates the order, which will be scheduled for the appointment requested./createOrder
FMO6Submit a Change Offer, Modify Attribute or Disconnect order at a location to modify or disconnect an active service.The API returns a 200 response and creates the order, which will be scheduled for the appointment requested./createOrder
FMO7Submit an amend order request on an open order at a location to manage and update the order.The API returns a 200 response and the order will be amended with the request type./amendOrder
FMO8Submit an cancellation request on an open order at a location to cancel itThe API returns a 200 response and cancels the order./cancelOrder
FMO9Submit various GET requests associated to an open order at a location.The API returns a 200 response and the requested data./orders/{orderId}/notifications
/orders/{orderId}/attachments
/getOrderDetails

Test data

Postman collection

We have provided a Postman collection file to make it easy to test this API, which includes examples of requests that will generate responses within the EMMA environment. This will also include successful responses and error codes.

Note: You’ll also require your Azure Client ID and Client Secret to obtain a token as part of the global variables. To request access, contact API Support.

The following scenarios are intended as a guide and for use in conjunction with the variable names and values, which must be set prior to running the Postman collection.

createOrder
Test caseOrder typeMarket SegmentSite VisitCSE (Public or Private)Test case comment
FMO1.1Connect PrimaryResidentialMandatoryOptionalFull install required
FMO1.2Connect PrimaryBusiness or EducationMandatoryOptionalFull install required
FMO1.3Connect PrimaryAnyMandatoryOptionalGreenfield or Fibre In a Day location
FMO2.1Connect PrimaryAnyNot returnedNot OfferedMDU/ROW consent, design and build required
FMO2.2Connect PrimaryAnyNot returnedNot OfferedManual feasibility required
FMO3.1Connect PrimaryResidentialOptionalOptionalIntact ONT activation
FMO3.2Connect PrimaryBusiness or EducationOptionalOptionalIntact ONT activation
FMO4.1Connect Additional ONTResidentialMandatoryOptional
FMO4.2Connect Additional ONTBusiness or EducationMandatoryOptional
FMO5.1Transfer PrimaryAnyOptionalOptional
FMO5.2Connect and ReplaceAnyOptionalOptional
FMO6.1Change OfferAnyMandatoryOptionalReplace ONT required
FMO6.2Modify AttributeAnyOptionalOptional
FMO6.3Disconnect PrimaryAnyNot returnedNot Offered
amendOrder
Test caseOrder typeamendOrderTypeTest case comment
FMO7.1Connect PrimaryanswerProvider to Advise
Note: To request this scenario, contact API Support with the Order IDs you want the corresponding question raised to answer on.
FMO7.2Connect PrimaryanswerQuote
Note: To request this scenario, contact API Support with the Order IDs you want the corresponding question raised to answer on.
FMO7.3Connect PrimaryanswerIntent to Cancel
Note: To request this scenario, contact API Support with the Order IDs you want the corresponding question raised to answer on.
FMO7.4Connect PrimaryanswerIntent to Disconnect
Note: To request this scenario, contact API Support with the Order IDs you want the corresponding question raised to answer on.
FMO7.5Connect PrimaryanswerIntent to Disconnect Secondary
Note: To request this scenario, contact API Support with the Order IDs you want the corresponding question raised to answer on.
FMO7.6Anyescalate
FMO7.7Anycharacteristic
FMO7.8Anyinteraction
FMO7.9AnyorderDetails
cancelOrder, getOrderNotifications, getOrderDetails, getOrderAttachmentDetails
Test caseOrder typeEndpoint
FMO8.1Any/orders/{orderId}
FMO9.1Any/orders/{orderId}/notifications
FMO9.2Any/{orderId}/attachments/{attachmentId}

Reviews