STATUS & DIAGNOSTICS
Check the connection.
Live feedback from the API, measured from your browser. No estimated uptime or simulated service results.
Live API check
This sends a small request to Sellix. A successful response means the API answered from your browser right now. It does not promise that every payment provider or background job is available.
Not checked yet
A check will run when this page loads.
No response yet.Health endpoint contract
GET https://api.sellix.gg/health requires no API key. A normal response is HTTP 200 with status: "ok" and an ISO-8601 server time.
The response time shown here includes the trip from your browser to the API and back. A slower result can come from your own network as well as the server.
Developer details
This is application liveness, not a readiness probe for the database, queue, mail delivery, webhook receivers or external payment providers. Latency is browser wall-clock round-trip time, not a server-side processing metric. No historical uptime dataset or incident feed is currently exposed here.
{"status":"ok","time":"2026-10-31T00:00:00+00:00"}The JSON above is the response shape. The live response is shown in the panel above.
Check your integration
If health works but an integration does not, check the API key, its permissions and the resource ID. You can test these independently without changing your account.
Open the API playground and run the read-only connection checks. Each check displays its actual HTTP result, timing and request ID. A 403 on orders with a products-only key is a permissions result, not a platform outage.
For help, include the request ID, endpoint, HTTP status and time of the failure. Keep API keys and payment credentials out of support messages.