Flow of Gameplay (Client Games)

It is required to prepare your own server (partner server) for your client game and make requests to Nutaku APIs through your server.

1. Make request from the client to your server.
2. Make request from your server to Nutaku API.
3. Process the response from Nutaku API on your server and return the relevant data to the client.

1. Requests to Nutaku API Server

To be able to utilize Nutaku APIs that support or require 3-legged OAuth authentication from your server, you need the user's authentication details (tokens). For that, you must first send a login request to the mobile api.

When you use Nutaku APIs in game, send the request to Nutaku API server (hereafter the API server). As the URL to be used for request, concatenate Endpoint URL and/or Query Parameter defined by each API (found on the API's documentation) to the main server URL (found on the platform configuration page).

Use UTF-8 for the request data, and express any emoji characters as Unicode text of docomo devices.

All requests sent to Nutaku API server must include an OAuth Authorization header. For more information how to generate an OAuth signature and Authorization header, check the 3-legged section from the How to use REST API page.

2. Response from Nutaku API server to your server

A response in JSON will be returned when you send an HTTP request to each API. The character code is UTF-8 and emoji characters are the same as Unicode text of NTT docomo device.

Most HTTP status codes in the responses are determined by each API. Status code 404 is returned for URLs that do not exist as NUTAKI APIs. Status code 501 is returned for an API which is default but not implemented.

See API reference for more details as per each API.