api:porting:poa-delete
Table of Contents
API : Porting POA Delete
Introduction
This request will delete a Power Of Attorney document received from the customer by email, fax or upload.
Multiple POA documents can be created and sent to the customer for signing and returning, e.g. if numbers are added or removed before the porting is ordered it might be necessary to create a new POA document.
When a porting is ordered it is important that only 1 POA document it sent to the donor operator and that it covers all the numbers (or more) that are part of the porting. Therefore all non-relevant documents must be delete ordering.
Only portings that are in one of these stages can have POA documents deleted:
- IN_CREATED
- IN_AWAITING_POA_FROM_CUSTOMER
- IN_POA_RECEIVED_FROM_CUSTOMER
- IN_POA_SENT (only ADMIN may delete at this stage)
- IN_ORDERED (only ADMIN may delete at this stage)
Request
| URL | https://api.telecomx.dk/porting/PORTING_ID/poa/delete/DOCUMENT_ID | |
|---|---|---|
| Method | GET | |
| Access level | OWNER if user belongs to the customer. RESELLER if customer belongs to the reseller. ADMIN. |
|
| Param | PORTING_ID | Id of the porting (24 hex-char string) |
| DOCUMENT_ID | Id of the POA document (24 hex-char string) | |
Query example
https://api.telecomx.dk/porting/1234567890ABCDEF12345678/poa/delete/1234567890ABCDEF12345678
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 |
| 400 | bad_request | Porting document not found in request URI |
| 403 | access_denied | Porting document cannot be deleted at this stage |
| 403 | access_denied | Insufficient access level |
| 404 | document | Porting document not found |
| 500 | internal_error | <Unspecified> |
api/porting/poa-delete.txt · Last modified: 2014/05/27 10:09 by Per Møller