Skip to main content

Try the Willow API for Free

You can try the Willow Admin API and User API without talking to sales. The Free plan costs $0, needs no credit card, and lets the person who creates the organization generate API tokens right away.

By the end of this page, you will have:

  • created a free Willow organization
  • generated a scoped API token (prefix wxt_)
  • listed your organization's MCP servers with curl
  • revoked the token when you are done

Prerequisites​

  • a work email address (personal providers such as Gmail are not accepted)
  • curl or any HTTP client

Step 1: Create a free organization​

Go to app.withwillow.ai/signup and sign up with Google, GitHub, or email. Your first sign-in creates a new organization on the Free plan and makes you its owner. Owners hold every admin permission, including creating API tokens.

Use a work email address. Personal email providers such as Gmail and Yahoo are rejected. If your company already uses Willow and restricts sign-ups from its domain, you are sent to that organization's admin instead.

See Willow pricing for what the Free plan includes.

Step 2: Generate an API token​

  1. In the admin dashboard, go to Admin > API Tokens.
  2. Select Generate Token.
  3. Name it (for example, "API trial") and select only the admin:read scope.
  4. Keep the default 90-day expiration, or pick 7 days for a trial.
  5. Select Generate and copy the token. It starts with wxt_ and is shown only once.

If an admin has turned on approval for new API tokens, the token stays pending until an admin with approval rights approves it. A new organization has approval turned off.

See API Tokens for every scope and how they combine.

Step 3: Make your first call​

Send the token as a bearer token to the Admin API. On Willow SaaS the base URL is https://app.withwillow.ai. On an EU, self-hosted, or custom-domain deployment, use the URL you open the admin dashboard at.

curl https://app.withwillow.ai/api/mcp-servers \
  -H "Authorization: Bearer wxt_xxxxx"

A successful response lists your organization's MCP servers with pagination details. A new organization may return an empty data array:

{
  "data": [],
  "pagination": { "cursor": 0, "limit": 100, "hasMore": false, "nextCursor": null }
}

A 401 means the token is missing, mistyped, or expired. A 403 means the token lacks the scope for that endpoint.

To call the User API, add a header that names the user to act as (x-user-email or x-machine-user) and use a connect:read token. See Using the Token.

Step 4: Revoke the token​

When you are done, go to Admin > API Tokens and select the revoke (trash) icon next to the token. Revoking takes effect immediately.

Test environment​

Willow has no separate sandbox or test mode, and there are no test API keys. Use a free organization as your test environment instead. It is a real, isolated organization, so anything you create there stays out of your production organization, and you can delete the trial resources or the token at any time.

For a safe trial:

  • give tokens only the scopes you need (admin:read cannot change anything)
  • set a short expiration
  • use a separate organization from your production one

Client libraries​

Willow does not publish official SDK packages. The APIs are described by OpenAPI 3 specs, which you can feed to any OpenAPI client generator:

APIOpenAPI spec
Admin APIadmin-api.yaml (JSON)
User APIuser-api.yaml (JSON)
SCIM APIscim-api.yaml (JSON)

Generate TypeScript types with openapi-typescript and call the API with openapi-fetch:

npx openapi-typescript https://docs.withwillow.ai/openapi/admin-api.yaml -o willow-admin-api.d.ts

Generate a Python client with OpenAPI Generator:

npx @openapitools/openapi-generator-cli generate \
  -i https://docs.withwillow.ai/openapi/admin-api.yaml \
  -g python -o willow-admin-client

The API catalog lists all three specs in machine-readable form.

Official packages​

These are the npm packages Willow publishes:

PackageWhat it does
@willowai/cliThe Willow CLI (willow): sign in, list, and call your MCP tools from a terminal, script, or CI. See Willow CLI.
@mcp-s/mcpA local STDIO MCP server that connects an MCP client to your Willow gateway. See Connect MCP.

Next steps​

On this page