Developer applications

Team-scoped applications organize your integration credentials on the developer portal. Each application groups API tokens and SDK keys under a named integration (for example “Production CRM sync” or “Marketing site SDK”).

Applications do not change how authentication works. The REST API and MCP server still use Sanctum personal access tokens with scoped abilities. Applications add structure, visibility, and usage rollups.

Create an application

1. Sign in at developer.formspring.io (or your local developer.* host).
2. Open Applications → New application.
3. Choose a type (api, mcp, sdk, webhook, or general).
4. Optionally add a website URL and redirect URIs.

Redirect URIs are stored for future OAuth support. They are not used for authentication today.

* * *

Link credentials

API tokens

When minting a token (UI or POST /api/v1/tokens), pass developer_application_id with the application's public_id. The token is tagged to that application for filtering and usage reporting.

SDK keys

When creating an SDK key on the developer host, pass developer_application_id in the form body. The key remains a public pfk_* env id for the survey loader.

MCP setup

The MCP setup wizard can attach tokens to an existing MCP-type application, or create one when create_application is set.

* * *

REST API

Applications are scoped to your current team at request time, matching other API resources.

* * *

Team integrations index

The developer portal also lists:

• Webhooks — every webhook on your team's forms, surveys, and funnels
• Automations — automations across those objects
• Usage — token activity rollups by application and source (api vs mcp)

Per-object webhook and automation editors remain in the dashboard; the developer host is the cross-team index.