SkidCord Developer Docs

Welcome to the SkidCord REST API

This documentation provides all the necessary endpoints for integrating the SkidCord infrastructure into your own applications, Discord bots, or web panels. We currently support JSON payloads and Bearer token authentication.

What Can You Build?

The SkidCord API is designed to turn our powerful proxy infrastructure into a scalable ecosystem. Here are some common use cases for developers:

Reseller & Store Integrations: Automatically generate, deliver, or revoke license keys when a customer makes a purchase on your Sellix, Shoppy, or custom storefront.
Discord Bot Automation: Verify if a user holds a valid SkidCord license and assign them special "Customer" or "Premium" roles automatically.
Proxy Automation for Bots: Programmatically rotate IP addresses, fetch live proxy lists, and monitor bandwidth usage directly from your custom scripts without needing the desktop UI.
Custom Dashboards: Build your own monitoring solutions to track active connections, proxy latency, and subscription status.

Authentication

This website contains documentation for the core SkidCord API. All requests require a unique API Key which you can obtain from the Developer Dashboard. This key must be sent as a Bearer token in the Authorization header of your requests.

BASH

curl -X GET "https://api.skidcord.net/v1/status" \
  -H "Authorization: Bearer sk_live_xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json"
                    

Security Warning

Never share your API key on the client-side (e.g., Frontend JavaScript) or in public GitHub repositories. If your key is compromised, immediately revoke and regenerate it from your dashboard.

Core Endpoints

1. License Verification

Verifies the validity of your users' SkidCord license keys.

Endpoint: POST /v1/licenses/verify

Request Body:

JSON

{
  "license_key": "SKID-XXXX-XXXX-XXXX",
  "hwid": "BFEBFBFF000906EA"
}
                    

Response (200 OK):

JSON

{
  "status": "success",
  "data": {
    "valid": true,
    "tier": "lifetime",
    "expires_at": null,
    "user": "admin",
    "hwid_match": true
  }
}
                    

2. Remote Injection

Sends a direct injection command to a SkidCord Client on a remote machine. (Only available for authorized API keys).

Endpoint: POST /v1/client/inject

JSON

{
  "client_id": "usr_982348923",
  "target_process": "Discord.exe",
  "module": "core_bypass_v2",
  "stealth_mode": true
}
                    

Tip

To track the status of injection operations, you can use the /v1/client/jobs/{job_id} endpoint or set up a Webhook.

Webhooks

SkidCord can send instant HTTP POST requests to your server whenever specific events occur in your applications.

license.expired - Triggered when a user's license expires.
client.injected - Triggered after a successful injection process.
hwid.reset_requested - Triggered when a user requests an HWID reset from the panel.

JSON (Example Payload)

{
  "event": "client.injected",
  "timestamp": 1718293812,
  "data": {
    "client_id": "usr_982348923",
    "status": "success",
    "duration_ms": 420
  }
}
                    

Rate Limits

To maintain server stability, the SkidCord API enforces IP and API Key-based rate limiting. You can monitor your remaining requests in the X-RateLimit-Remaining response headers.

Plan Type	Request Limit	Refresh Period
Starter	30 requests	Per minute
Premium	120 requests	Per minute
Advanced	1000 requests	Per minute

Error Codes

If you exceed the limit or send invalid data, the API will return a standard JSON error.

HTTP Status	Code (JSON)	Description
400	invalid_request	The submitted parameters are missing or incorrect.
401	unauthorized	The API Key is missing or invalid.
403	hwid_mismatch	The license key is correct, but the HWID does not match.
404	not_found	The requested resource could not be found.
429	rate_limited	You have sent too many requests, please wait.
500	internal_error	There is a temporary failure on the SkidCord servers.