Hosted page
Responsive pages, clear sender context, validation, private or shared links, expiry, and submission limits.
Input, files, and approvals from people
Your software creates the request and sends the returned Fangst URL through its existing email channel. The recipient uploads the documents on a clear hosted page.
Put your case id in metadata, send the hosted URL with your own email provider, and receive the files against that case.
POST https://api.fang.st/v1/requests
Authorization: Bearer <FANGST_API_TOKEN>
Content-Type: application/json
{
"title": "Missing documents",
"sender": "Example Accounting",
"metadata": {
"case_id": "case_510"
},
"fields": [
{
"key": "receipts",
"type": "files",
"required": true
}
]
}{
"status": "completed",
"response": {
"company_name": "Northstar AS"
}
}Software uses the HTTP resources directly. Authorized AI agents can use the same API or intention-oriented Fangst MCP tools.
POST/v1/requestsCreate a hosted request and receive its URL.GET/v1/requests/:idRead request status and configuration.GET/v1/requests/:id/submissionsRead completed responses.MCPrequest_human_inputLet an authorized agent create the request.MCPget_human_inputLet the agent read the completed response.Responsive pages, clear sender context, validation, private or shared links, expiry, and submission limits.
Typed values, authenticated file downloads, correlation metadata, timestamps, and stable response ids.
Polling, signed webhooks, retries with backoff, delivery history, idempotency, and replay.
Start with $1 free. Add funds from $10. Links, polling, webhooks, and abandoned requests do not use the main billable unit.
Create the hosted interaction through Fangst and receive the structured result back.