Jinko Public API

REST discovered

Details

URL: https://api.gojinko.com
Docs: https://docs.gojinko.com/api-reference/introduction

Authentication

Jinko API key (`jnk_*`) X-API-Key: <credential> + Jinko API key (`jnk_*`) Authorization: Bearer <credential> discovered

Jinko API key (`jnk_*`) api_key Get key ↗

Sign in at Jinko dashboard keys, click Create key, give it a name, and copy the jnk_ key when shown. Sandbox uses separate keys from production; generate the sandbox key from the same dashboard while targeting the sandbox environment documented in API keys.

Jinko CLI OAuth token (device flow) oauth2 discovered Set up OAuth ↗

Authorization: Bearer <credential>

Install the CLI from Connect via CLI, then run jinko auth login and choose the OAuth browser sign-in path. The CLI prints a device URL and code; open the URL, approve access, and the CLI stores and refreshes the resulting token in ~/.jinko/config.yaml. This token works for the CLI and REST /v1 bearer auth, but the docs say it cannot be reused as a bearer token on the MCP endpoint.