EShop

The Nintendo 3DS eShop was added in the June 2011 update for JP/EUR/USA.

From here, you can download Virtual Console games, 3D Classics, DSiware software, view screenshots, and 3D trailers for upcoming 3DS titles.

While eShop is loading, eShop will use command NIMS:CheckSysupdateAvailableSOAP. If a system update is available where title installation for system titles still needs finalized (or when the updated titles were not downloaded at all), eShop will then display the “system update is available” message.

The eShop application uses command AMNet:FinishInstallToMedia to finalize the SD title install (if the whole title is downloaded while eShop is still running), however, before using that command the eShop application also uses AMNet:FinishInstallToMedia to finalize installing all system titles (from system updates).

eShop QR Codes can be scanned with the camera, allowing one to quickly navigate to the desired eShop title with just two clicks. The QR Codes themselves is a simple text/url QR, started with “ESHOP://” string followed by a decimal eShop content link id(same IDs used internally by eShop for all content) and then some special data, delimited by a dot symbol, which can be ommited.

In order for the QR-code string data to be valid for eShop, it must begin with “ESHOP://5”, with the first ID being all decimal.

• New QR Code for Japanese “Photos with Super Mario” has a different code string: ESHOP://50010000013120.J00108Z00001.CD588EAE95A3A68D15C647DA2AC0945FD88F70AB8A31149E51C4B05FB927B0B8

• There is a link in the Japanese eShop [http://www.nintendo.co.jp/3ds/eshop/qrCode.html?####] where you can replace the #### with the Japanese eShop title’s serial and you will get it’s QR code. (i.e. 🔗 http://www.nintendo.co.jp/3ds/eshop/qrCode.html?JCAJ will get you the pushmo QR code)

• You could use Google’s Chart API to create a QR code from the codes above: 🔗 https://chart.googleapis.com/chart?chs=150x150&cht=qr&chl=ESHOP (replace the ESHOP text with the ESHOP:// link from one of the above)

This section describes the 0x1C-byte structure stored at the application parameters from APT:StartApplication, under the 0x300-byte buffer listed there.

The ExtData File System for eShop is as follows:

root
├── icon
├── boss
│   └── TIGER100.tmp
└── user

The eShop pulls its music from a static, region-specific link in a format similar to the following:

🔗 https://a248.e.akamai.net/f/248/103046/10m/npdl.c.app.nintendowifi.net/p01/nsa/CtfKXACbUPl8s7lk/BGM1/<region>_BGM1, where region is one of the primary system regions (JP, US, EU, KR, etc.) Support also exists for ‘BGM2’, but this seems to be unused. The music is held in a BOSS container.

The format consists of a brief XML header describing the audio (including the date it was set as the main eShop theme, loop times, size, etc) followed by a raw AAC stream. Tools such as FFmpeg can handle rebuilding this stream with ADTS headers for proper time info and such.

The Home Menu uses nearly the same format for the Theme Shop’s background music.

eShop uses the following domains over HTTPS:

• cp3s-auth.c.shop.nintendowifi.net
• a248.e.akamai.net
• ninja.ctr.shop.nintendo.net
• samurai.ctr.shop.nintendo.net
• ccif.ctr.shop.nintendo.net
• eou.c.shop.nintendowifi.net

These domains are used by NIM:

• nus.c.shop.nintendowifi.net
• ecs.c.shop.nintendowifi.net
• cas.c.shop.nintendowifi.net

ninja.ctr.shop.nintendo.net and samurai.ctr.shop.nintendo.net contain the bulk of the eShop information.

Requests with the following parameters will always return XML unless the header “Accept: application/json” is used, in which case JSON will be returned.

For every request to the ninja and samurai servers, three parameters are always sent, though are not necessarily required:

samurai.ctr.shop.nintendo.net (samurai) provides metadata about titles. The samurai server provides the backend for the eShop title search.

Common parameters described above can always be sent.

ninja.ctr.shop.nintendo.net (ninja) contains the seeds for the new 9.6 crypto, pricing information and handles actions that require authentication, such as purchases. Authentication information seems to be obtained from the act:u sysmodule and works through OAuth2.

The eShop application itself uses a RootCertChain for all HTTPS requests, all of the trusted root CAs are the following default ones:

• CertID 0x3
• CertID 0x6
• CertID 0x7
• CertID 0x8
• CertID 0x9
• CertID 0xA

Pre-v10.0 eShop used an URL like this: “%s/samurai/ws/%s/title/%llu/other_purchased?shop_id=1&lang=%s&_type=json”. That URL was removed with v10.0. That URL was requested when trying to load eShop app-pages. Following the maintenance mentioned above, this page was removed from the server, which broke pre-v10.0 eShop app whenever it tried to access that page.

URL changes between 9.7.0-25 and 10.0.0-27 are (green = add, red = remove):

%s/ninja/ws/%s/titles/online_prices?title%%5B%%5D=%s&lang=%s&include_coupon=true&shop_id=1&_type=json

%s/ninja/ws/%s/coupon/!check?shop_id=1&_type=json

%s/ninja/ws/my/owned_coupons?ns_uid=%llu&shop_id=1&_type=json

%s/ninja/ws/my/owned_coupons?shop_id=1&_type=json

%s/ninja/ws/my/parental_control/!put?shop_id=1&_type=json

%s/ninja/ws/%s/title/%llu/prepurchase_info?%s=%s&shop_id=1&_type=json

%s/samurai/ws/%s/coupon/%llu/titles?lang=%s&limit=%u&offset=%u&shop_id=1&_type=json

%s/ninja/ws/my/auto_billing/plans?limit=%u&offset=%u&shop_id=1&_type=json

%s/ninja/ws/%s/titles/online_prices?title%%5B%%5D=%s&lang=%s&include_coupon=true&coupon_id=%llu&shop_id=1&_type=json

%s/ninja/ws/my/auto_billing/%014llu/!cancel?shop_id=1&_type=json

%s/samurai/ws/%s/title/%llu/other_purchased?shop_id=1&lang=%s&_type=json

%s/samurai/movie/%s/%s/%014llu/moflex

CheckNew3DS is called in two functions. This is only used for disabling UI button(s) for downloading New3DS titles when running on Old3DS. For example, on a New3DS patching a CheckNew3DS func-call with <retval=0>, results in the download button on the app page being grayed-out for a New3DS-only title.

Attempting to download a New3DS-only title with an Old3DS eShop account(even with a New3DS using an Old3DS account), results in the ninja server(specifically the “prepurchase_info” page) returning an error. HTTP 400 is returned with the following json reply:

000000: 7b 22 65 72 72 6f 72 22 3a 7b 22 63 6f 64 65 22  {"error":{"code"
000010: 3a 22 33 31 35 36 22 2c 22 6d 65 73 73 61 67 65  :"3156","message
000020: 22 3a 22 54 68 69 73 20 70 72 6f 64 75 63 74 20  ":"This product 
000030: 63 61 6e 6e 6f 74 20 62 65 20 70 75 72 63 68 61  cannot be purcha
000040: 73 65 64 5c 6e 6f 72 20 72 65 64 65 65 6d 65 64  sed\nor redeemed
000050: 20 66 6f 72 20 75 73 65 20 6f 6e 20 74 68 69 73   for use on this
000060: 20 73 79 73 74 65 6d 2e 5c 6e 5c 6e 49 66 20 74   system.\n\nIf t
000070: 68 65 20 70 72 6f 62 6c 65 6d 20 70 65 72 73 69  he problem persi
000080: 73 74 73 2c 20 70 6c 65 61 73 65 5c 6e 6d 61 6b  sts, please\nmak
000090: 65 20 6e 6f 74 65 20 6f 66 20 74 68 65 20 65 72  e note of the er
0000a0: 72 6f 72 20 63 6f 64 65 20 61 6e 64 5c 6e 76 69  ror code and\nvi
0000b0: 73 69 74 20 73 75 70 70 6f 72 74 2e 6e 69 6e 74  sit support.nint
0000c0: 65 6e 64 6f 2e 63 6f 6d 2e 22 7d 7d              endo.com."}}

There’s titleID checks in the system eShop application code for “Pokémon Omega Ruby”. This appears to be used with UI-related code, unknown why.