Update document
Update a document with any content type (text, url, file, etc.) and metadata
Body ParametersJSON
Optional tag this document should be containerized by. This can be an ID for your user, a project ID, or any other identifier you wish to use to group documents.
(DEPRECATED: Use containerTag instead) Optional tags this document should be containerized by. This can be an ID for your user, a project ID, or any other identifier you wish to use to group documents.
The content to extract and process into a document. This can be a URL to a website, a PDF, an image, or a video.
Plaintext: Any plaintext format
URL: A URL to a website, PDF, image, or video
We automatically detect the content type from the url’s response format.
Optional custom ID of the document. This could be an ID from your database that will uniquely identify this document.
When this document’s content is from, as opposed to when it was uploaded. Accepts YYYY-MM-DD or a full ISO 8601 timestamp. Memory extraction resolves relative dates (‘yesterday’, ‘last quarter’) against this instead of the ingestion time, and documents in a batch are processed oldest-first so newer facts correctly supersede older ones. Set this whenever you backfill historical content.
Update document
curl https://api.supermemory.ai/v3/documents/$ID \
-X PATCH \
-H 'Content-Type: application/json' \
-H "Authorization: Bearer $SUPERMEMORY_API_KEY" \
-d '{
"containerTag": "user_alex",
"content": "Our API rate limits are 100 req/min on free and 1000 on pro. Clients should use exponential backoff on 429s.",
"customId": "doc-api-rate-limits",
"documentDate": "2025-03-14",
"filepath": "/documents/reports/file.pdf",
"filterByMetadata": {
"department": "engineering",
"region": "us"
},
"metadata": {
"source": "upload",
"language": "en"
},
"taskType": "memory"
}'{
"id": "id",
"status": "status"
}Returns Examples
{
"id": "id",
"status": "status"
}