Skip to content
Skills Library
Programming · Testing

api-exploration

/api-exploration

Workflow for testing Fusebase API calls interactively using temporary tokens. Use when: 1. You need to verify an API endpoint behavior before writing app code, 2. You want to explore available API responses or schemas, 3. You're unsure how an API endpoint works and need to test it, 4. Debugging API integration issues by making direct calls.

Licence
MIT
Last repository change
19.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Workflow for testing Fusebase API calls interactively using temporary tokens. Use when: 1. You need to verify an API endpoint behavior before writing app code, 2. You want to explore available API responses or schemas, 3. You're unsure how an API endpoint works and need to test it, 4. Debugging API integration issues by making direct calls.

Original author description

Workflow for testing Fusebase API calls interactively using temporary tokens. Use when: 1. You need to verify an API endpoint behavior before writing app code, 2. You want to explore available API responses or schemas, 3. You're unsure how an API endpoint works and need to test it, 4. Debugging API integration issues by making direct calls.

How it works

  1. Workflow
  2. Example: Testing @fusebase/dashboard-service-sdk
  3. Key Points
Original SKILL.md headings · 101 lines, 363 words
SKILL.md preview
---
name: api-exploration
description: "Workflow for testing Fusebase API calls interactively using temporary tokens. Use when: 1. You need to verify an API endpoint behavior before writing app code, 2. You want to explore available API responses or schemas, 3. You're unsure how an API endpoint works and need to test it, 4. Debugging API integration issues by making direct calls."
---

# API Exploration with Temporary Tokens

When you're unsure about an API endpoint's behavior, response shape, or want to test a flow before committing to implementation — create a temporary token and run test calls directly.

## Workflow

### 1. Create a temporary token

```bash
fusebase token create --app <appId>
```

This outputs a short-lived token (15 min) to stdout. Capture it:

```bash
TOKEN=$(fusebase token create --app <appId>)
```

The `appId` comes from `fusebase.json` → `apps[].id`.

### 2. Write and run test code

Create a temporary script (e.g. `_test-api.ts`) to make the API calls you want to verify:

```typescript
const token = process.env.TOKEN || "<paste-token-here>";

const res = await fetch("https://api-endpoint/...", {
  headers: { "x-app-feature-token": token },
});
console.log(res.status);
console.log(await res.json());
```

Run it:

```bash
TOKEN=$(fusebase token create --app <appId>) bun _test-api.ts
```

### 3. Inspect results and iterate

Read the output, adjust your calls, and re-run. Once you understand the API behavior, implement it properly in your app code.

### 4. Clean up

Delete the temporary test script when done — don't commit it.

## Example: Testing `@fusebase/dashboard-service-sdk`

Use this to verify SDK calls before wiring them into app UI code.

`_test-sdk.ts`:

```typescript
import {
  createClient,
  DatabasesApi,
  CustomDashboardRowsApi,
} from "@fusebase/dashboard-service-sdk";

const token = process.env.TOKEN!;
const BASE_URL =
  "https://app-api.{FUSEBASE_HOST}/v4/api/proxy/dashboard-service/v1";

const client = createClient({
  baseUrl: BASE_URL,
  defaultHeaders: { "x-app-feature-token": token },
});

const dbApi = new DatabasesApi(client);
const rowsApi = new CustomDashboardRowsApi(client);

// List databases visible to this app
const dbs = await dbApi.listDatabases({});
console.log("databases:", JSON.stringify(dbs, null, 2));

// Read rows from a specific dashboard view
const rows = await rowsApi.getRows({
  dashboardId: "<dashboardId>",
  viewId: "<viewId>",
});
console.log("rows:", JSON.stringify(rows, null, 2));
```

Run it:

```bash
TOKEN=$(fusebase token create --app <appId>) bun _test-sdk.ts
```

Replace `BASE_URL` host with the value matching your environment's `FUSEBASE_HOST` (e.g. `app-api.thefusebase.com` for prod).

## Key Points

- Token expires in **15 minutes**. Create a new one if it expires.
- Use this for **any** Fusebase API call you want to validate — dashboard data, app endpoints, etc.
- The API spec is available at the public OpenAPI endpoint if you need to discover available routes.
- Prefix test files with `_` (e.g. `_test-sdk.ts`) so they're easy to spot and clean up.

Versions

RepositoryScoreLicence
This page · fusebase-dev/fusebase-flow100MIT
sozercan/kaset100MIT
ryan-haver/fusebase-mcp100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 801f3ba1eee9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95fusebase-cli
    Complete guide for using the Fusebase CLI (fusebase) tool to initialize, develop, and deploy Fusebase Apps apps. Use when: 1. Initializing new Fusebase Apps projects, 2. Creating or configuring apps, 3. Running apps locally or deploying them 4. Setting up app permissions for dashboards.
  • 95fusebase-cli
    Complete guide for using the Fusebase CLI (fusebase) tool to initialize, develop, and deploy Fusebase Apps apps. Use when: 1. Initializing new Fusebase Apps projects, 2. Creating or configuring apps, 3. Running apps locally or deploying them 4. Setting up app permissions for dashboards.
  • 100fusebase-flow-health-check
    Use when the operator asks "is Fusebase Flow healthy", "check Fusebase Flow", "did fusebase update break anything", "Fusebase Flow status", "restore Fusebase Flow", or asks whether Fusebase CLI and Fusebase Flow agent files conflict. Runs the read-only health engine, reports…
  • 100api-testing
    Use when writing API endpoint tests — integration tests, contract validation, response assertions, mocked external services — even when the user says 'test this route' without naming API testing.
  • 100automating-api-testing
    Test automate API endpoint testing including request generation, validation, and comprehensive test coverage for REST and GraphQL APIs. Use when testing API contracts, validating OpenAPI specifications, or ensuring endpoint reliability. Trigger with phrases like "test the API",…
  • 100automating-api-testing
    Test automate API endpoint testing including request generation, validation, and comprehensive test coverage for REST and GraphQL APIs. Use when testing API contracts, validating OpenAPI specifications, or ensuring endpoint reliability. Trigger with phrases like "test the API",…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.