Apps and their data APIs in Chile
Chile's carrier self-care market: mobile, fibre and home-pack apps, and the subscriber data APIs behind them.
Chile's hub covers the incumbent mobile-and-fibre self-care client. Mi Movistar Chile is Telefónica Chile's official app: an OpenID access_token then returns postpaid boletas with fechaVencimiento and montoTotal, prepaid saldo versus postpaid deuda, a profile keyed by rutCliente, and technician visits under apptNumber.
The same session tracks product orders (orderId, offeringId), service tickets and device-biometric enrolment — the endpoints behind every bill, balance and field-visit screen in the app.
Frequently asked questions
Which analyzed apps operate in Chile?
The Chile hub covers Mi Movistar Chile, Telefónica Chile's official self-care app, documenting the API behind its boleta, saldo, deuda, technician-visit and product-order screens.
What subscriber data does the Mi Movistar API expose?
Signed-in calls return postpaid boletas (fechaEmision, fechaVencimiento, montoTotal, montoPendiente, cicloFacturacion), prepaid saldo versus postpaid deuda, a profile (rutCliente, nombreCliente, numeroCliente, customerId), technician slots (apptNumber, horario) and product orders (orderId, productId, offeringId).
How does the Mi Movistar app authenticate?
POST /v1/movistar/login exchanges an authorization_code plus PKCE code_verifier (grant_type, client_id) for access_token, refresh_token, id_token and expires_in. Later first-party calls send Authorization: Bearer. Device biometrics can enrol and verify on the same session. There is no public developer key for these endpoints.
