Skippr Docs

Appearance

Get started with Skippr Cloud ​

Skippr Cloud exposes managed identity, data, messaging, compute, and edge capabilities over HTTPS APIs. This page takes you from authentication to one successful CloudTables.ListTables call in eu-central-1.

  • Status: Preview.
  • First operation: CloudTables.ListTables (supported).
  • Endpoint: https://tables.eu-central-1.cloud.skippr.io.
  • Authentication in this example: Cloud JWT.
  • Contract: ListTables operation.

Before you start ​

You need an email address that can sign in to the Cloud directory. Skippr Cloud derives your tenant from the verified token. Do not send a tenant id in a request body, query parameter, or custom header.

For CI, Terraform, or CDKTF, use an operator or workload SigV4 key instead. See Auth credentials after completing the JWT path.

1. Request a one-time code ​

bash
curl -sS -X POST https://auth.cloud.skippr.io/auth/sign-in \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com"}'

The response confirms that a code was requested. Retrieve the code from your email.

2. Exchange the code for a token ​

bash
curl -sS -X POST https://auth.cloud.skippr.io/auth/confirm \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com","code":"123456"}'

The response includes:

  • token: access JWT used as Authorization: Bearer …;
  • refresh_token: long-lived token used with /auth/refresh.

Store both as secrets. Do not commit them to source control.

3. Make your first Cloud call ​

Set the access token returned by the confirmation request:

bash
export CLOUD_BEARER_TOKEN='<token>'

curl -sS https://tables.eu-central-1.cloud.skippr.io/ \
  -H "Authorization: Bearer ${CLOUD_BEARER_TOKEN}" \
  -H 'Content-Type: application/json' \
  -H 'X-Cloud-Target: CloudTables.ListTables' \
  -d '{}'

A successful response returns a JSON tableNames array and may include an opaque nextToken when more results are available.

If the request fails ​

  • 401: the token is missing, malformed, or expired. Refresh or sign in again.
  • 403: your tenant policy does not permit the operation.
  • 404: confirm the service hostname and exact X-Cloud-Target value.
  • 429: wait before retrying; edge rate limits apply per caller.

Cloud JSON errors use code, message, and requestId. See the shared error contract.

Choose your next path ​

  • Direct API: use the service index to choose a capability, then check exact readiness in the operation index.
  • Terraform: declare supported cloud_* resources with provider skippr/cloud. Start with Terraform and CDKTF providers.
  • CDKTF TypeScript or Python: synthesize the same Terraform resources with @skippr/provider-cloud or skippr-cdktf.
  • Build a tenant API: create routes and integrations with Gateway.