Table of Contents
API : Porting Order
Introduction
This request will order the porting at OCH (Danish central phone numbers database). The ordering will send a request to the donor operator, asking them to release the number(s) on a given date. The donor operator will then confirm the requested date or set a later date if they have a valid reason for doing so, or they may reject the porting.
Before the porting is ordered, a requested date that has passed or falls on a weekend or Danish holiday is moved to the next business day (a RESELLER_ADMIN or ADMIN may keep today). Once ordered, the date has been agreed with the donor operator and is not moved again.
When ordering a porting there can be a delay between calling the order request and it to be actually carried out. This is because some operator requires a delay between receiving the POA document and the order going through. If this is the case, the property autoStartOrder is set and will contain the date and time the order will be sent.
Request
| URL | https://api.telecomx.dk/porting/PORTING_ID/order | |
|---|---|---|
| Method | GET | |
| Access level | RESELLER_ADMIN with PORTING feature. | |
| Param | PORTING_ID | Id of the porting (24 hex-char string) |
Query example
https://api.telecomx.dk/porting/1234567890ABCDEF12345678/order
Response
| Json object | ||
|---|---|---|
| success | Boolean | True if request was sucessful. |
Example
{ success: true }
Errors
| Error code | Message | Description |
|---|---|---|
| 400 | bad_request | Porting id not found in requested URI |
| 403 | stage | Porting is not at the right stage to be ordered |
| 409 | id | An outporting cannot be ordered |
| 500 | internal_error | Failed to lookup operator 'X' |
| 409 | documents | Porting cannot be ordered, because no porting documents (POA) exists |
| 409 | operator | Donor operator updated on porting, POA not valid anymore |
| 404 | not_found | Porting not found |
| 500 | internal_error | <Unspecified> |