API reference
Every resource in the Partner API, one page per resource with the object model first and each operation beneath it.
Each resource page opens with the object and every one of its fields, then lists every operation with its parameters, request body, responses and the permission its API key needs, beside an example panel that follows you down the page. Only operations available to partners are shown here.
Users
The people who hold a line: create them, keep their details current, and remove them when they leave.
Numbers
The line you sell: obtain one, list and look them up, replace a lost SIM, stop and restore service, and end it.
Port-ins
Bring a number from another carrier: discover the fields each country needs, validate, submit and track the port.
Usage
Raw voice, SMS and data records as one chronological feed.
Analytics
Consumption aggregated per interval, for reporting and dashboards.
Data pools
How much of each shared pool is left, and what each member has used.
Rates
Pay-as-you-go prices for a market: calls and messages per destination, roaming data per visited country.
Conventions
- Base URL:
https://api.telgea.com - Authentication: the
x-api-keyheader on every request. Each operation names the permission its key needs. - Identifiers are UUIDs; phone numbers are E.164; dates are
YYYY-MM-DD; timestamps are ISO 8601 in UTC. - Lists page with
page(from 1) andpageSize, and returnitemsCount, the total across pages. The usage feed pages with a cursor instead. Each operation states its own maximum page size. - Every failure returns an RFC 9457 Problem Details body (
application/problem+json) withtype,title,status,detail,codeandrequestId; a validation failure addsfields, one entry per rejected field. See Errors. - Each API key allows 1000 requests per 24 hours, shared across every endpoint; a request over the budget returns
429. - Every
POST,PATCHandDELETEaccepts an optionalIdempotency-Keyheader, so a retry after a dropped connection returns the original response instead of doing the work twice.
Try it
The playground lists every operation with a working example. There is no sandbox: calls run against your own live organization with your own key.
Machine-readable description
The complete OpenAPI description, including every example on these pages: /openapi.