Telecom subscription

Report telecom subscription disconnection events to Ropo One.

This guide explains how to report telecom subscription disconnections to Ropo One.

Use this when the subscription has been disconnected on your side and the event must be reported to Ropo One.

This documentation describes the Ropo One interface (REST API) and message format (JSON). If these capabilities do not fit your system, other interfaces and message formats can be agreed separately during implementation.

Services

Disconnected

When a telecom subscription is disconnected on the client side after a disconnection request from Ropo One, report the action to Ropo One.

Example message:

{
  "customernumber": "A123456",
  "description": "Telecom subscription disconnected",
  "id": "1a2b3c4d5",
  "status": "disconnected",
  "time": "2024-01-04 10:41:40"
}

customernumber identifies the end customer whose telecom subscriptions were disconnected.

API interface for delivering telecom subscription events

post

Authorizations

bearerAuth

AuthorizationstringRequired

Bearer authentication header of the form Bearer <token>.

Body

application/json

TelecomSubscriptionEvent

statusstringOptional

Type of event

Example: disconnected

customernumberstringOptional

Customer number identifying the debtor

Example: A123456

timestringOptional

Time when the event occurred

Example: 2026-05-06 10:00:00

descriptionstringOptional

Further description of the event

Example: Subscription closed due to unpaid debt

Responses

200

Successful operation

No content

400

Bad request

application/json

401

Unauthorized

post/telecomsubscription/event

HTTPcURLJavaScriptPython

POST /rest/telecomsubscription/event HTTP/1.1
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 136

{
  "status": "disconnected",
  "customernumber": "A123456",
  "time": "2026-05-06 10:00:00",
  "description": "Subscription closed due to unpaid debt"
}

No content