Guides / Support

Status and support

If something looks wrong with your connection, check the status as shown below first. If that does not solve it, contact technical support.

Check connectivity

The root URL of each API returns a service description without a key. If these return 200 but other requests fail, the problem is most likely your key, plan or limits.

bash
# Service description endpoints that respond without a key: 200 means you reached the API server
curl -s -o /dev/null -w "%{http_code}\n" https://api.chickstockfi.com/openapi/v1
curl -s -o /dev/null -w "%{http_code}\n" https://api.chickstockfi.com/openapi/pro/v1
  • 401 · 403: see Authentication and Errors.
  • 429: check the headers described in Rate limits.
  • If 503 keeps coming back or the root URL does not respond, let technical support know.

Technical support

What to include

  • The request time (KST) and the API you called (Data API · PRO API · MCP)
  • The method and path (for example Samsung Electronics · 005930 GET /openapi/v1/quotes/005930) and query parameters
  • The HTTP status, the error.code from the response, and response headers such as X-Quota-Remaining
  • The key prefix shown in the console (for example ck_live_8fA2c1…). Never send the full key.