MyASUS - Service Center is ASUSTeK COMPUTER INC.'s official after-sales client for owners of ASUS and ROG PCs, motherboards, phones and accessories. After an ASUS Account sign-in, the home tabs switch among Service, Account, Message Center, Market Event and Store. Service opens product registration, repair-status lookup by serial or RMA number, a map of authorized repair centers, online chat, TMSS question forms and (in some locales) Zentalk and repair reservation; Account holds the membership card — blue, gold, diamond, employee or ROG — with a barcode and QR of the member code, EXP and point history, the owned-product list and profile; Message Center pages unread ASUS notices; Market Event lists campaigns the member can join. Copy and repair-server routing follow a 59-locale service map that covers Taiwan, the United States, India, Indonesia, Korea, Germany, Brazil, Vietnam and the other ASUS regions, sitting beside the desktop MyASUS for Windows rather than a third-party repair tracker.
Registered serials on an ASUS Account carry warrantyStart and warrantyEnd windows plus a categoryType of WEP or WEP,Upgrade Service. Live RMAs expose itemStatus codes such as ACCEPT, REPAIR, SHIP and WAIT-WB1 together with rmaNo, serialNo and a progressBar. Owned units list serial_no, ProductMarketName, purchase_date and register_date.
The membership card adds Points, Levels, Mcode and memberLevelName (blue, gold, diamond, employee or ROG), with expLogList and pointLogList paging the loyalty ledger behind them. Nearby authorized shops return SCName, Address, GPSLat and GPSLng. The Message Center inbox reports per-sender unread counts beside Sender_Name, Sender_Icon and the lastShortMessages preview, and Market Event campaigns list eventName, eventCode and noteLink per locale. IT desks can watch fleet warranties and RMA queues, CRM stacks can keep the ASUS loyalty ledger, and store locators can pin service centers — openData Studio turns those records into callable open data.
Screenshots
API surface
The endpoints and request/response examples below are reconstructed from the app's interface — illustrative, not a live capture.
Sign in to an ASUS Account
POST
/v1/myasus/sessionosintAuthenticates an ASUS Account and returns the Ticket and CusId that later member, product and message calls attach.
Auth: None. Body is loginJson with Account and Password. Status 0 returns Result.Ticket and Result.CusId; Message values password error and login error map to client code 21.
- Account
- Password
- Status
- Message
- Result
- Ticket
- CusId
POST /v1/myasus/session HTTP/1.1 Content-Type: application/json; charset=utf-8 { "Account": "[email protected]", "Password": "********" }{ "Status": 0, "Message": "OK", "Result": { "Ticket": "tk-8f21a4c2", "CusId": "C123456789" } }Fetch ASUS Account profile
POST
/v1/myasus/profileosintReads the signed-in profile: name, address, member code Mcode, Points, Levels, card ExpiredTime (shown as memberCardExpiredDate) and AcceptEDM.
Auth: ASUS Account Ticket from sign-in (body field ticket).
- ticket
- Status
- Message
- Result
- Account
- FirstName
- LastName
- NickName
- Birthday
- Addr1
- Addr2
- City
- Zipcode
- Country
- HomeVoice
- Professional
- Education
- Mcode
- Points
- Pic
- ExpiredTime
- ExperienceValue
- CashValue
- Levels
- IsEmployee
- Active
- Gender
- AcceptEDM
POST /v1/myasus/profile HTTP/1.1 Content-Type: application/json; charset=utf-8 { "ticket": "tk-8f21a4c2" }{ "Status": 0, "Message": "OK", "Result": { "Account": "[email protected]", "FirstName": "Ada", "LastName": "Chen", "NickName": "Ada", "Birthday": "1990-04-12", "Addr1": "115 Li-Te Rd", "City": "Taipei", "Zipcode": "112", "Country": "TW", "HomeVoice": "+886-2-2894-3447", "Email": "[email protected]", "Professional": "Engineer", "Education": "BSc", "Mcode": "A123456789", "Points": 2400, "Pic": "https://example.com/pic/a123.png", "ExpiredTime": "2027-12-31T00:00:00", "ExperienceValue": 18500, "CashValue": 0, "Levels": 2, "IsEmployee": false, "Active": true, "Gender": "Female", "AcceptEDM": true } }Renew ASUS Account ticket
POST
/v1/myasus/session/refreshosintExchanges the current Ticket and CusId for a fresh Ticket so later member and message calls stay signed in.
Auth: Existing Ticket plus CusId from sign-in (fields oldTicket and cusId). Status 0 returns Result.Ticket.
- Ticket
- CusId
- Status
- Message
- Result
POST /v1/myasus/session/refresh HTTP/1.1 Content-Type: application/json; charset=utf-8 { "Ticket": "tk-8f21a4c2", "CusId": "C123456789" }{ "Status": 0, "Message": "OK", "Result": { "Ticket": "tk-renewed-91ab" } }Start an ASUS ID authorization code
POST
/v1/myasus/oauth/authorizeosintOpens the ASUS ID PKCE authorize step that later exchanges for an access_token used on repair and event calls.
Auth: HTTP Basic (ASUS ID client id and secret). Body is PKCE: response_type=code, redirect_uri, scope, state, code_challenge, code_challenge_method=S256. HTTP 200 returns the authorization payload; failures carry error_description.
- response_type
- redirect_uri
- scope
- state
- code_challenge
- code_challenge_method
- code
- error_description
POST /v1/myasus/oauth/authorize HTTP/1.1 Content-Type: application/json; charset=utf-8 Authorization: Basic ******** { "response_type": "code", "redirect_uri": "https://localhost/callback.aspx", "scope": "member profile ticket", "state": "st-8f21a4c2", "code_challenge": "a1b2c3d4e5f6", "code_challenge_method": "S256" }{ "code": "ac-91ab33de", "state": "st-8f21a4c2" }Exchange ASUS ID code for access_token
POST
/v1/myasus/oauth/tokenosintTrades the authorization code for an access_token (cached as tokenId) that RMA, WEP and campaign headers attach.
Auth: HTTP Basic (ASUS ID client id and secret). Body grant_type=client_code plus scope, code, state and code_verifier from the authorize step. HTTP 200 returns access_token and expires_in.
- grant_type
- scope
- code
- state
- code_verifier
- access_token
- expires_in
- error_description
POST /v1/myasus/oauth/token HTTP/1.1 Content-Type: application/json; charset=utf-8 Authorization: Basic ******** { "grant_type": "client_code", "scope": "member profile ticket", "code": "ac-91ab33de", "state": "st-8f21a4c2", "code_verifier": "pkce-verifier-********" }{ "access_token": "at-asusid-91ab", "expires_in": 3600 }Mint a UCS signing seed
POST
/v1/myasus/repair/signing-seedosintReturns the UCS seedType and seed that the client combines into the tokenId sent as Authorization on RMA and WEP calls.
Auth: Authorization Basic from the repair-service credential vault. JSON body cactus plus sandSoil (SHA-256 of the vault sandSoil value). message Success returns result.seedType and result.seed.
- cactus
- sandSoil
- message
- result
- seedType
- seed
POST /v1/myasus/repair/signing-seed HTTP/1.1 Content-Type: application/json; charset=utf-8 Authorization: Basic ******** { "cactus": "********", "sandSoil": "<sha256-of-vault-value>" }{ "message": "Success", "result": { "seedType": "sign", "seed": "sd-8f21a4c2" } }Read membership card
POST
/v1/myasus/membership/cardopendataReturns the membership card shown on Account: memberLevelName (blue/gold/diamond/employee/ROG), Mcode used as barcode and QR, Points and Levels. Card-type map in the card WebView is 1=blue, 2=gold, 3=employee, 4=diamond, 999=ROG.
Auth: ASUS Account Ticket from sign-in (field ticket).
- ticket
- Status
- Message
- Result
- memberLevelName
- memberLevel
- memberPoint
- Mcode
- Points
- Levels
- ExpiredTime
POST /v1/myasus/membership/card HTTP/1.1 Content-Type: application/json; charset=utf-8 { "ticket": "tk-8f21a4c2" }{ "Status": 0, "Message": "OK", "Result": { "memberLevelName": "Gold", "memberLevel": 2, "memberPoint": 2400, "Mcode": "A123456789", "Points": 2400, "Levels": 2, "ExpiredTime": "2027-12-31T00:00:00" } }Page membership EXP history
POST
/v1/myasus/membership/exp-logopendataPages the EXP ledger shown on ExpLogActivity: memberExp / memberNextLevelExp, memberExpiredTime, memberLevel, memberLevelName, and Result.expLogList.
Auth: ASUS Account Ticket from sign-in. Body carries ticket plus page index.
- ticket
- page
- Status
- Message
- Result
- expLogList
- memberExp
- memberNextLevelExp
- memberExpiredTime
- memberLevel
- memberLevelName
POST /v1/myasus/membership/exp-log HTTP/1.1 Content-Type: application/json; charset=utf-8 { "ticket": "tk-8f21a4c2", "page": 1 }{ "Status": 0, "Message": "OK", "Result": { "memberExp": 18500, "memberNextLevelExp": 20000, "memberExpiredTime": "2027-12-31", "memberLevel": 2, "memberLevelName": "Gold", "expLogList": [ { "exp": 200, "date": "2026-09-01", "note": "Product registration" } ] } }Page membership point history
POST
/v1/myasus/membership/point-logopendataPages the point ledger shown on PointLogAndEventActivity into Result.pointLogList.
Auth: ASUS Account Ticket from sign-in. Body carries ticket plus page index.
- ticket
- page
- Status
- Message
- Result
- pointLogList
POST /v1/myasus/membership/point-log HTTP/1.1 Content-Type: application/json; charset=utf-8 { "ticket": "tk-8f21a4c2", "page": 1 }{ "Status": 0, "Message": "OK", "Result": { "pointLogList": [ { "point": 50, "date": "2026-08-12", "eventName": "Summer campaign" } ] } }List owned registered products
GET
/v1/myasus/products/ownedopendataPages every product registered on the CusID for My Product: serial_no, model, ProductMarketName, purchase_date and register_date.
Auth: Catalog CallerID and CallerPW plus the signed-in CusID. Query also sends GetProductImage=true, PageIndex, PageSize and timestamp t.
- CallerID
- CallerPW
- CusID
- GetProductImage
- PageIndex
- PageSize
- t
- StatusCode
- Message
- cus_id
- serial_no
- model
- type
- ProductMarketName
- purchase_date
- register_date
- ProductImgFilePath
GET /v1/myasus/products/owned?CallerID=vip&CallerPW=********&CusID=C123456789&GetProductImage=true&PageIndex=1&PageSize=20&t=1760000000 HTTP/1.1{ "StatusCode": 0, "Message": "OK", "Products": [ { "cus_id": "C123456789", "serial_no": "M7N0CV123456789", "model": "ASUS_AI2205", "type": "Phone", "ProductMarketName": "ROG Phone 8", "purchase_date": "2024-03-18", "register_date": "2024-03-20", "ProductImgFilePath": "//www.example.com/media/global/products/rogphone8_end_100.png" } ] }Register a product serial
POST
/v1/myasus/products/registeropendataRegisters serial SN onto the signed-in CusID so it appears in the owned-product list and can be used for RMA and warranty checks.
Auth: Catalog CallerID and CallerPW plus the signed-in CusID. Form body also sends SN. StatusCode 1 is success.
- CallerID
- CallerPW
- CusID
- SN
- StatusCode
- Message
POST /v1/myasus/products/register HTTP/1.1 Content-Type: application/x-www-form-urlencoded CallerID=vip&CallerPW=********&CusID=C123456789&SN=M7N0CV123456789{ "StatusCode": 1, "Message": "OK" }Look up RMA items by serial or RMA number
GET
/v1/myasus/repairs/itemsopendataReturns open repairItemList and closedItemList for an RMA or serial: itemStatus (ACCEPT, APPLY, REPAIR, SHIP, CLOSED, WAIT-WB1 and related codes), rmaNo, serialNo, center, dates and progressBar.
Auth: Authorization header is the repair-service tokenId from the seed/token flow. Query is rmaNo or serialNo (uppercased).
- rmaNo
- serialNo
- message
- result
- repairItemList
- closedItemList
- applyNo
- lineNo
- rmaCenter
- rmaCenterName
- rmaCenterPhone
- itemStatus
- itemStatusDesc
- productType
- country
- productPnDesc
- entryDate
- applyDate
- receiveDate
- closedDate
- name
- phoneNo
- shippingTypeDesc
- progressBar
- progressIndex
- status
GET /v1/myasus/repairs/items?serialNo=M7N0CV123456789 HTTP/1.1 Authorization: tok-repair-91ab{ "message": "Success", "result": { "repairItemList": [ { "applyNo": "A24010001", "lineNo": "1", "rmaCenter": "RC-TPE-01", "rmaCenterName": "ASUS Taipei SC", "rmaCenterPhone": "+886-2-2894-3447", "rmaNo": "R24010001", "serialNo": "M7N0CV123456789", "itemStatus": "REPAIR", "itemStatusDesc": "In repair", "productType": "Phone", "country": "TW", "productPnDesc": "ROG Phone 8", "entryDate": "2026-09-01T10:00:00", "applyDate": "2026-08-28T09:00:00", "receiveDate": "2026-09-02T14:00:00", "closedDate": "", "name": "Ada Chen", "phoneNo": "+886900000000", "shippingTypeDesc": "Carry in", "progressIndex": 3, "progressBar": [ {"status": "ACCEPT"}, {"status": "RECEIVE"}, {"status": "REPAIR"} ] } ], "closedItemList": [] } }Find nearby ASUS service centers
GET
/v1/myasus/service-centers/nearbyopendataReturns authorized repair centers near lat/lng for the Service map: SCName, Address, Phone, Hours, Products, GPSLat and GPSLng.
Auth: None. Query website, cname, lat, lng and optional product. Status SUCCESS returns Result.Obj.
- website
- cname
- lat
- lng
- product
- Status
- Message
- Result
- Obj
- SCName
- Address
- Phone
- Hours
- Products
- GPSLat
- GPSLng
GET /v1/myasus/service-centers/nearby?website=usa&cname=USA&lat=37.386&lng=-122.084 HTTP/1.1{ "Status": "SUCCESS", "Message": "OK", "Result": { "Obj": [ { "SCName": "ASUS Service Center - Fremont", "Address": "48720 Kato Rd, Fremont, CA", "Phone": "+1-510-739-3777", "Hours": "Mon-Fri 09:00-18:00", "Products": "Notebook, Desktop, Phone", "GPSLat": "37.548", "GPSLng": "-121.988" } ] } }Check extended-warranty (WEP) window
POST
/v1/myasus/warranty/extend-checkopenfinanceReads the paid Warranty Extension Program window for a serial: warrantyStart, warrantyEnd and categoryType WEP or WEP,Upgrade Service.
Auth: Authorization header is the repair-service tokenId from the seed/token flow. HTTP code 200 with result.resultCode 1062 is WEP, 1057 is WEP,Upgrade Service.
- sn
- code
- message
- result
- resultCode
- resultDesc
- warrantyStart
- warrantyEnd
- categoryType
POST /v1/myasus/warranty/extend-check HTTP/1.1 Authorization: tok-repair-91ab Content-Type: application/json; charset=utf-8 { "sn": "M7N0CV123456789" }{ "code": 200, "message": "OK", "result": { "resultCode": 1062, "resultDesc": "Eligible", "warrantyStart": "2024/03/18", "warrantyEnd": "2027/03/18", "sn": "M7N0CV123456789", "categoryType": "WEP" } }Count unread inbox messages
POST
/v1/myasus/inbox/unread-countopendataReturns data.unread, the badge count on Message Center.
Auth: Form fields device, device_type, device_id, Ticket (ASUS Account ticket) plus AppID and AppKey from the app vault.
- device
- device_type
- device_id
- Ticket
- AppID
- AppKey
- code
- data
- unread
POST /v1/myasus/inbox/unread-count HTTP/1.1 Content-Type: application/x-www-form-urlencoded device=android&device_type=phone&device_id=adid-8f21&Ticket=tk-8f21a4c2&AppID=myasus&AppKey=********{ "code": "0", "data": { "unread": 3 } }List inbox senders and latest messages
POST
/v1/myasus/inbox/sendersopendataReturns the Message Center sender list: Sender_Name, Sender_Icon, unread, lastShortMessages and date (yyyy/MM/dd HH:mm:ss).
Auth: Form fields device, device_type, device_id, Ticket (ASUS Account ticket) plus AppID and AppKey from the app vault. code 0 returns data as the sender array.
- device
- device_type
- device_id
- Ticket
- AppID
- AppKey
- code
- data
- Sender_Cus_ID
- asus_member
- Sender_Name
- Sender_Icon
- already_read
- unread
- lastMessageId
- lastShortMessages
- date
POST /v1/myasus/inbox/senders HTTP/1.1 Content-Type: application/x-www-form-urlencoded device=android&device_type=phone&device_id=adid-8f21&Ticket=tk-8f21a4c2&AppID=myasus&AppKey=********{ "code": "0", "data": [ { "Sender_Cus_ID": "C0001", "asus_member": 1, "Sender_Name": "ASUS Service", "Sender_Icon": "https://example.com/icon/service.png", "already_read": 0, "unread": 2, "lastMessageId": 4412, "lastShortMessages": "Your RMA R24010001 is in repair.", "date": "2026/09/12 14:22:01" } ] }List market-event activities
POST
/v1/myasus/campaignsopendataLists Market Event campaigns for the locale website, using optional ticket and entryId filters.
Auth: Headers token (ASUS ID token) and apiid for the event service. JSON body status, website, optional entryId and ticket, count.
- token
- apiid
- status
- website
- entryId
- ticket
- count
- message
- result
- data
- eventName
- eventCode
- noteLink
POST /v1/myasus/campaigns HTTP/1.1 Content-Type: application/json; charset=utf-8 token: tok-asusid-******** apiid: myasus-event-service { "status": 1, "website": "usa", "entryId": "", "ticket": "tk-8f21a4c2", "count": 0 }{ "status": 200, "message": "OK", "result": { "data": [ { "eventName": "ROG summer cup", "eventCode": "EV-2026-08", "noteLink": "https://www.example.com/event/rog-cup" } ] } }List support product lines
GET
/v1/myasus/support/product-linesopendataReturns the product-line list the customer-support FAQ flow uses to pick Phone, Notebook and other families for a website locale.
Auth: None. Query website (locale support-site code). Status SUCCESS returns Result.Obj.Products.Items for the customer-support product picker.
- website
- Status
- Message
- Result
- Obj
- Products
- Items
- id
- name
GET /v1/myasus/support/product-lines?website=usa HTTP/1.1{ "Status": "SUCCESS", "Message": "OK", "Result": { "Obj": { "Products": { "Items": [ { "id": "pd-phone", "name": "Phone" }, { "id": "pd-nb", "name": "Notebook" } ] } } } }
Data categories
- warranty
- rma
- membership
- service-centers
- product-registration
- profile
- inbox
Where teams use this data
Fleet warranty dashboard
An IT desk that buys ASUS notebooks and ROG phones in bulk can pull warrantyStart, warrantyEnd and categoryType per serial_no and flag units whose WEP window is about to close.
RMA queue for helpdesks
A corporate helpdesk can poll repairItemList by serialNo, surface itemStatus (REPAIR, SHIP, WAIT-WB1) and closedDate, and route the user to rmaCenterName when the unit is still in house.
Service-center locator
A store-finder or maps overlay can drop SCName pins from GPSLat/GPSLng with Address, Phone, Hours and Products for the user's website locale.
Membership ledger sync
A CRM that already holds the customer's ASUS Account can copy Points, Levels, memberLevelName and Mcode, then append expLogList and pointLogList as loyalty events.
Frequently asked questions
How does MyASUS authenticate the owner?
ASUS Account sign-in returns Ticket and CusId. A ticket-refresh call issues a fresh Ticket. Member, EXP and point calls send that Ticket; product-catalog calls send CusID with CallerID and CallerPW; warranty and RMA calls send an Authorization tokenId minted from the signing-seed step.
What does itemStatus mean on an RMA?
Each repair line carries itemStatus and itemStatusDesc. The result screen maps codes such as ACCEPT, APPLY, RECEIVE, REPAIR, FINALTEST, PACK, SHIP, CLOSED, TRANSFER and WAIT-WB1 through WAIT-WB10 onto the progressBar. Open lines sit in repairItemList; finished lines sit in closedItemList with closedDate.
Which membership card types exist?
The card WebView maps API types 1=blue/normal, 2=gold, 3=employee, 4=diamond and 999=ROG onto memberLevelName. Mcode is rendered as both a barcode and a QR on the membership screen, next to Points, Levels and ExpiredTime.
Which markets does the service map cover?
The bundled region table has 59 locales (zh_TW, en_US, en_IN, in_ID, ko_KR, de_DE, pt_BR, vi_VN and others) with RepairServer codes AAS/AEU/AAM/AAU, WEP countryCode flags and home tabs SERVICE, ACCOUNT, MSG_CENTER, MARKET_EVENT and STORE. This catalog tags the United States, India, Indonesia, Korea, Germany, Brazil and Vietnam.
Apps similar to MyASUS - Service Center
- Lenovo — Lenovo's official Android app (listed as Lenovo, formerly Lenovo Help) lets owners of Lenovo PCs, tablets and phones look up warranty status, find a nearby service provider on a map, open a service ticket and check PC repair status.
- HP Support Assistant — HP Support Assistant Mobile is HP's official support client for PCs and printers, with guided troubleshooters, a Virtual Agent, a Service Center Locator and device-status views such as battery, storage and printer ink.
- Dell SupportAssist — Dell SupportAssist is Dell's official Android diagnostics-and-support app that checks device health, reviews hardware diagnostic results and connects owners to Dell support resources.
- Samsung Members — Samsung Members is Samsung's official Galaxy support app, with device diagnostics such as battery and camera checks, 1-on-1 expert chat and a community of Galaxy owners.
- Apple Support — Apple Support is Apple's official help app for personalized product solutions, chat or guided troubleshooting, and booking a Genius Bar or Apple Authorized Service Provider visit.
- MyMSI membership — MyMSI is MSI's official membership app for three-step barcode product registration, web-ticket support, live chat and push updates on those tickets.
- Carlcare — Carlcare is Transsion's official after-sales app for checking spare-parts prices and warranty, tracking repair status, finding the nearest service center and reserving a repair.
Topics
- MyASUS API
- ASUS RMA itemStatus
- ASUS warrantyStart warrantyEnd
- ASUS membership Points Mcode
- ASUS service center GPSLat
- ROG WEP extend warranty
- ASUS product registration serial_no
Need this app's data API integrated?
We deliver scoped integrations for any named app — from USD 500 with source-code handoff, or hosted access billed per call. Tell us the data you need.
- NDA + SOW on every engagement
- Delivery in 3–7 days
- Payment only after acceptance
- Work scoped to authorized use