> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/developer-guide/platform-api/data-world-model/intake-links.md).

# Intake Upload Links

Migration guidance for the retired standalone intake upload-link system, with links to authenticated dataset intake and patient-facing Surfaces.

{% hint style="warning" %}
The standalone shareable upload-link system has been retired. Its link-management, public upload, and link-scoped download endpoints are no longer available in the Platform API.
{% endhint %}

Use [dataset intake](/developer-guide/platform-api/data-world-model/intake.md) for authenticated ingestion into a registered dataset. For supported patient-facing forms, use [Surfaces](/developer-guide/platform-api/conversations/surfaces.md). These have different data lifecycles: a Surface submission does not automatically become a dataset file.

Existing integrations using upload links need a replacement collection workflow agreed with Concurrence. Do not continue distributing links from the retired system.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/developer-guide/platform-api/data-world-model/intake-links.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.