Apps and their data APIs in Saudi Arabia
Saudi Arabia's social-insurance and electricity market: GOSI wages and SANED, SEC bills and kWh, and the data APIs behind them.
Saudi Arabia's hub pairs the Riyadh social-insurance client with the national electricity self-care app. GOSI is the General Organization for Social Insurance's official app: a Nafath confirm issues an accessToken, then wage rows return contributoryWage and monthlyContributoryWage, certificates expose certificateNumber, and SANED sits as kSanedBenefit.
Saudi Energy is Saudi Electricity Company's consumer client: a Rayah OTP mints the session, then contract-account rows return totalDueAmount and meterNumber, Hasibati estimates pin ForecastBillAmount, and outage tickets add ticketNumber. The same GOSI session hydrates estimatedPension, ibanAccountNo and employer establishmentRegistrationNo.
Frequently asked questions
Which analyzed apps operate in Saudi Arabia?
The Saudi Arabia hub covers GOSI, the official social-insurance app of the General Organization for Social Insurance, and Saudi Energy, Saudi Electricity Company's self-care client — documenting the APIs behind wage, SANED, contract-account bill, kWh and outage screens. Amazon Seller and Urban Company Partner are also tagged for the market.
What data do the Saudi apps expose?
GOSI signed-in calls return contributoryWage and monthlyContributoryWage, certificateNumber, estimatedPension, kSanedBenefit and ibanAccountNo. Saudi Energy returns totalDueAmount, meterNumber, ForecastBillAmount, PrepaidBalance and ticketNumber.
How do the Saudi apps authenticate?
GOSI: POST /v1/gosi/nafath starts a Nafath confirm; POST /v1/gosi/session exchanges it for accessToken. Saudi Energy: POST /v1/electricity/auth/otp sends a Rayah OTP; POST /v1/electricity/auth/session validates it. Later first-party calls send Authorization: Bearer. There is no public developer key for these endpoints.
