Cliplus

Connection test

Prove your key works, from this page

Paste your own API key. This page calls the live hub with it — same base URL, same Authorization: Bearer header, same custom header your code will send — and generates a real clip at the resolution you pick. Every HTTP status code is shown exactly as it came back.

Your key is used only by your browser to call the hub directly. It is never sent to this site's servers and is not stored anywhere unless you tick "remember on this device".

1. Your credentials

Create one in the dashboard → API keys. A key is shown once, at creation.

Filled in from your deployment. Same for every customer; only the key differs.

Fixed for this test: 24 fps, ratio auto (16:9). 480p is the base tier and the cheapest real job the hub can run. Pick anything higher and the same call returns that resolution — it just costs more and takes longer to finish. Nothing about how it gets there changes your code.

2. What gets sent

Exactly these headers, on every call. The key is masked here, not in the request.

Authorization: Bearer <your key>
Content-Type: application/json
x-cliplus-client: cliplus-web-tester

3. Result

  • 1 Hub is aliveGET /healthz —
  • 2 Key is acceptedGET /v1/models —
  • 3 Job acceptedPOST /v1/videos —
  • 4 Job finishedGET /v1/videos/{id} —

Not run yet.

Your clip

The finished video appears here.

Raw response

The last response body, verbatim. This is the shape your code will parse.

{}

The same test as curl

Copy this if you would rather prove it from a terminal, or from CI.

—