Skip to content

imink API Documentation

Jone Wang edited this page Aug 30, 2022 · 25 revisions

You are free to use these APIs, but you need to set the proper User-Agent and let me know you are using it. Thanks!


F API (2022-8-24 Update)

More information about the 2022-8-24 update. (Thanks to @samuelthomas2774 for the information)

I created a new project for the f API. To learn more please visit here.

URL:

POST https://api.imink.app/f

Body:

JSON

  • token : String, Required. Get it from NSO api
  • hash_method : Number or String, Required. 1 or 2
  • timestamp : Number or String, Optional. It is not recommended to use this parameter
  • request_id : String, Optional. It is not recommended to use this parameter

NOTE: timestamp and request_id will be generated by the server if not submitted. It is recommended to use the api generated timestamp and request_id. If you try to submit your own timestamp, it may cause the NSO api to return a 9599 error.

Example:

curl -X "POST" "https://api.imink.app/f" \
     -H 'User-Agent: {{ Your app name }}/{{ Your app version }}' \
     -H 'Content-Type: application/json; charset=utf-8' \
     -d $'{
  "token": "{{ token }}"
  "hash_method": {{ 1 or 2 }},
}'

Response:

{
  "request_id": "c6e9d62d-7c05-4c9a-8f1a-b6d799fdd5ff",
  "timestamp": 1661355877196,
  "f": "543f7e9c4f3d3b5254a3772d211a8c093888b32991002c353f278bc8766face4b548f1bdaea24c9a58e5012b"
}

Note: As of 2022-8-23, timestamp must be submitted to the NSO api with a numeric type instead of a string type.

This API must be used in the login flow to calculate the f parameter. It is generated by the NSO client on the imink server.

Login Flow

Battle Schedule API

Request:

curl "https://api.imink.app/schedules" \
     -H 'User-Agent: {{Your app name}}/{{Your app version}}'

Salmon Run Schedule API

Request:

curl "https://api.imink.app/salmonrun_schedules" \
     -H 'User-Agent: {{Your app name}}/{{Your app version}}'
Clone this wiki locally