Request files with one API call.

Your software or AI agent specifies the files it needs. Fangst returns a hosted upload link. The person uploads the files, and your system receives the result.

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.

Collect documents for a customer case.

Attach your own customer and case identifiers as private metadata, then receive the uploaded files against the right record.

Create

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

{
  "title": "Customer documents",
  "metadata": {
    "customer_id": "cus_123"
  },
  "fields": [
    {
      "key": "contract",
      "type": "file",
      "required": true
    },
    {
      "key": "supporting_files",
      "type": "files"
    }
  ]
}

Completed result

{
  "status": "completed",
  "attachments": [
    {
      "id": "file_01",
      "name": "contract.pdf"
    }
  ]
}

What a production file-request flow needs.

A file request is more than an upload field. The request must identify the right case, limit what can be submitted, protect the uploaded files, and tell your software when the response is ready.

Correlate every upload

Keep customer, case, or transaction identifiers in private metadata so filenames never become your database key.

Constrain the request

Define required files, accepted content types, file counts, byte limits, expiry, and submission limits before sharing the link.

Retrieve files safely

Receive stable attachment ids in the response, then download the encrypted files through the authenticated API.

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