AI agents and API integration

For developers and AI assistants

FillFaster publishes a plain Markdown “skill” file that any agent or LLM can retrieve over HTTPS. It explains what the product is, which workflows exist, and where the canonical OpenAPI contract lives. It does not duplicate every endpoint; always use OpenAPI for exact shapes.

Stable URLs

Resource	URL
Human overview (this page on the help site)	https://help.fillfaster.com/developers/ai-agents
Agent / LLM skill (markdown)	https://help.fillfaster.com/.well-known/agent-skills/fillfaster-api/SKILL.md - installable folder; discovery index at /.well-known/agent-skills/index.json
OpenAPI 3 (JSON)	https://help.fillfaster.com/fillfaster-openapi.json
Interactive API reference (Scalar)	https://help.fillfaster.com/developers/api
Webhooks guide	https://help.fillfaster.com/developers/webhooks/

Suggested agent behavior

1. Fetch /.well-known/agent-skills/fillfaster-api/SKILL.md first for workflow context.
2. Fetch fillfaster-openapi.json (or use a local copy from your monorepo) for all endpoint and schema details.
3. Follow the authentication scheme defined in OpenAPI (API token).
4. Design submission flows around webhooks per form; use status polling only when push notifications are not possible.
5. On every create submission (POST /v1/createSubmission, including bulk), put recipient_name under user_data by default.

Recipient name in the dashboard

user_data.recipient_name is optional in the API schema and highly recommended. The dashboard Submissions list and Search use it as the recipient name. A name you only put in prefill_data does not appear there, so API-created links look unidentified until you send this field.

Include it on the default payload:

{
  "fid": "<form template id>",
  "user_data": {
    "recipient_name": "Jane Recipient"
  }
}

recipient_email stays optional. Set it only when FillFaster should email the signing link. If you set recipient_email, also set recipient_name.

If you maintain Cursor rules or a project skill, point them at the same two URLs so humans and tools stay aligned.