Collect customer documents through your API.

Create a document request for a customer, supplier, or applicant. Fangst hosts the upload page and returns every file to the correct case in your software.

Start free See the API example

From API call to structured result.

Create the requestSoftware or an AI agent defines the fields and receives a hosted URL.
Share the URLA person opens the Fangst page and provides the requested input or files.
Read the resultFangst returns structured data through the API or a signed webhook.

Request a known set of documents.

The hosted page shows exactly what is missing and keeps the response connected to your internal case id.

Create

POST https://api.fang.st/v1/requests
Authorization: Bearer <FANGST_API_TOKEN>
Content-Type: application/json

{
  "title": "Documents we need",
  "metadata": {
    "case_id": "case_92831"
  },
  "fields": [
    {
      "key": "identity",
      "type": "file",
      "required": true
    },
    {
      "key": "proof_of_address",
      "type": "file",
      "required": true
    }
  ]
}

Completed result

{
  "status": "completed",
  "response": {
    "company_name": "Northstar AS"
  }
}

Model document collection around the case, not the inbox.

Create the request when your system knows what is missing. The hosted page gives the recipient one clear checklist, while private metadata keeps the returned documents attached to the correct record.

Declare what is missing

Use one required file field per known document and an optional multi-file field for supporting material.

Preserve system context

Store the internal case id as metadata instead of exposing database identifiers in instructions or filenames.

Continue from completion

Use a signed webhook when the case can advance immediately, or poll when your application owns the schedule.

Use REST, MCP, polling, or webhooks.

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.

Fangst runs the hosted interaction.

Hosted page

Responsive pages, clear sender context, validation, private or shared links, expiry, and submission limits.

Structured result

Typed values, authenticated file downloads, correlation metadata, timestamps, and stable response ids.

Reliable delivery

Polling, signed webhooks, retries with backoff, delivery history, idempotency, and replay.

Pay for completed interactions. No subscription.

Start with $1 free. Add funds from $10. Links, polling, webhooks, and abandoned requests do not use the main billable unit.

See pricing

Give your software a way to ask people.

Create the hosted interaction through Fangst and receive the structured result back.

Contact