FousSSO e-Service
Turn the SSO e-Service into an API
Read your contribution history, transaction statuses and insured-person checks from the SSO e-Service with one API call each. A workflow can check on the 10th of each month which สปส.1-10 submissions still show a ชำระเงิน link or status P.
Works with your own SSO e-Service account. Fous is an independent product.
What you can build on the SSO e-Service
Get contribution history
Build thisReads รายการประวัติการส่งเงินสมทบ (contribution history) for one employer account, branch and Buddhist Era year.
- Takes
- Employer account number, branch number, year (Buddhist Era)
- Returns
- Contribution period, payment date, wages, contribution rate, insured persons, contributions, surcharge paid
Check transaction status
Build thisReads ตรวจสอบสถานะในการทำธุรกรรม (transaction status): your transactions of one type, how each was entered, whether it shows a ชำระเงิน link and its status.
- Takes
- Employer account number, transaction type, branch (optional), date range (optional)
- Returns
- Transaction number, date, transaction type, period, branches, entry method (K or U), ชำระเงิน link shown or not, status (Y, P or C)
Check whether a person is insured
Build thisChecks a national ID number in ตรวจสอบสถานะผู้ประกันตน (insured person status): whether the person is insured and whether they are under one of your branches.
- Takes
- National ID number
- Returns
- National ID number, insured or not, under your establishment or not, message shown
Submit monthly contribution data
Build thisKeys in a สปส.1-10 for one branch under ส่งข้อมูลเงินสมทบ: each employee's ID number, name and wages, then confirms with ยืนยันการส่งข้อมูล.
- Takes
- Branch number, month and year, employees with national ID number, title, first name, surname, wages
- Returns
- Transaction number, period, total wages, employee contributions, employer contributions, total contributions, insured persons
Automate the SSO e-Service with a workflow
A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.
สปส.1-10 submissions still unpaid or in status P
Build this- Starts
- Every month on the 10th at 9:00, Asia/Bangkok
- Step 1
- Check transaction status for contribution transactions made since the 1st.
- Step 2
- Keep the ones that still show a ชำระเงิน link or are in status P.
- Step 3
- Email you the list with transaction number, date, transaction type, period, entry method and status.
Insured status of new hires, back to your HR system
Build this- Starts
- When your HR system calls the workflow's webhook with new hires' national ID numbers
- Step 1
- For each national ID number, check the person's insured status.
- Step 2
- Keep the people not insured, or insured but not under your branches.
- Step 3
- Post them to your HR system's webhook with national ID number, insured or not, and the message shown.
Paid contribution periods per branch, to accounting
Build this- Starts
- Every month on the 20th at 8:00, Asia/Bangkok
- Step 1
- For each branch you name, get this year's contribution history.
- Step 2
- Keep the periods not there on the last run.
- Step 3
- Post them to your accounting system's webhook with branch, period, payment date and amounts.
You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.
Once built, one call from your code
Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get contribution history” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "www.sso.go.th/get_contribution_history",
"input": {
"employer_account_number": "1012345678",
"branch": "000000",
"year_be": 2569
}
}'
{
"status": "completed",
"data": {
"employer_account_number": "1012345678",
"branch": "000000",
"year_be": 2569,
"periods": [
{
"contribution_period": "09/2569" ,
"payment_date": "14/10/2569" ,
"wages": 286400,
"contribution_rate": 5,
"insured_persons": 18,
"contributions": 28640,
"surcharge_paid": 0
}
],
"count": 1
}
}
An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.
The SSO e-Service’s own options
The e-Service user manual describes no API for employers. Contribution data for a สปส.1-10 is keyed in or uploaded as a file on the portal, registration data can be uploaded as a สปส.1-04 file, and contribution history, insured status and transaction status are read on screen. You need an e-Service account approved by the Social Security Office.
| Option | What it covers | What it takes |
|---|---|---|
| Contribution file upload (แนบไฟล์) | A month's contribution data for one branch or several, as .txt, .dat, .csv, .xls or .xlsx, or encrypted as .gpg or .enc. | An approved e-Service account with rights for the branches you send for. For encryption, the SSO's GPG public key with SHA-256. |
| Registration file (สปส.1-04) | Insured-person registration data sent as an uploaded file under ทะเบียนผู้ประกันตน. | An approved e-Service account with rights for that establishment and branch. |
| Exports from transaction status | Per transaction: an export of its data, the สปส.1-10 report, and the file that was uploaded. | An approved e-Service account. Transactions can be searched back at most 2 years. |
| The SSO e-Service by hand | Registration, contribution submission, payment by QR Code, e-Payment or at a service counter, contribution history and status checks. | A username and password issued by the Social Security Office after it approves your สปส.1-05 request. |
Read on November 12, 2026: E-Services user manual for employers, SSO e-Service for employers.
Signing in to the SSO e-Service
The SSO e-Service signs you in with a username (ชื่อผู้ใช้) and password, issued by email once the Social Security Office approves your request, and you change the password on first sign-in. With Fous you sign in once through the e-Service's own sign-in with your own account: the login is sealed with AES-256, code and AI agents never see it, and an expired session is signed back in.
Worth knowing
- The account comes after an approval
- You apply under ขอทำธุรกรรมผ่านอินเตอร์เน็ต, then file the สปส.1-05 it emails you with the Social Security Office. The username and password arrive by email after approval.
- Rights are given per branch
- A user works only for the establishment and branches it holds rights for. More branches and rights are requested under เปลี่ยนแปลงสิทธิ์ในการทำธุรกรรม, which files a สปส.1-05 change request.
- Two years back, and only P can be cancelled
- Transaction status searches go back at most 2 years. Only a transaction in status P can be cancelled, and e-receipts exist only for e-Payment.
- A payment QR code lasts one day
- You pay by QR Code, by e-Payment through your bank, or at a service counter with the emailed สปส.1-10. A payment QR code is valid until 23:59:00 on the day it is created.
More in Government: East and South-East Asia, Oceania
- 登記情報提供サービス
- Cổng thông tin hóa đơn điện tử
- SIPP Online
- Edabu
- PhilHealth EPRS
- Virtual Pag-IBIG for Employers
- KWSP i-Akaun (Majikan)
- 自然人电子税务局(扣缴端)
- eMPF Platform
- My.SSS Employer Portal
- BIR eFPS
- RD e-Filing
- 全国统一规范电子税务局
- Coretax DJP
- myIR
- MyTax
Other industries: FBR IRIS, Trip.com eBooking, SECOP II, Egyptian Tax Authority e-Services, Plataforma de Contratación del Sector Público, MOT Testing Service.
Frequently asked questions
Not one the e-Service user manual describes. Employers key in contribution data or upload it as a .txt, .dat, .csv, .xls or .xlsx file, optionally GPG-encrypted, upload registration data as a สปส.1-04 file, and read results on screen. With Fous you build methods on your own account that return those screens as JSON.
Open ตรวจสอบสถานะในการทำธุรกรรม. Each transaction shows its status as Y, P or C, and only a P transaction can still be cancelled. K or U shows how the data was entered, and a transaction still to be paid shows a ชำระเงิน link.
Yes, with ส่งเงินสมทบแบบยื่นรวมสาขา, which files a สปส.1-10/1 covering several branches in one go. The account needs rights for each of those branches. For a single branch you use ส่งเงินสมทบแบบแยกยื่น and a สปส.1-10.
Yes. Under ทะเบียนผู้ประกันตน, choose แจ้งสิ้นสุดการเป็นผู้ประกันตน (สปส.6-09), enter the national ID number, the date and the reason, and confirm. The system emails a receipt of the สปส.6-09.
No. Fous is an independent product. You use it with your own SSO e-Service account, and a method reads and does only what that account can.
Put SSO e-Service behind an API call
Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextBIR eFPSRD e-Filing全国统一规范电子税务局FBR IRISHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of SSO e-Service (สำนักงานประกันสังคม (Social Security Office), Thailand). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.