Recued
Menu
← Back to packs

Documents, Uploads, and Vaults - Basecamp

by recued-core v1 app_pack 5 views

Basecamp document, upload metadata, version, folder, and vault operations over JSON-representable routes. Generated from Basecamp's commit-pinned official OpenAPI 3.1 contract. The OAuth connection owns the bearer token and fixed https://3.basecampapi.com origin; every operation requires an explicit numeric accountId target and sends Basecamp's mandatory identifying User-Agent. Read caching is disabled. Every document, upload-metadata, version, folder, and vault read is marked sensitive-read and requires approval unless session-granted. Unsafe 64-bit JSON identifiers are preserved as exact decimal strings, and int64 request identifiers are accepted as strings and serialized without numeric rounding. Every mutation is grant-off and approval-gated.

What this pack installs

  • basecamp-content Ingredient

Trust & control

What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.

What it's allowed to do

Write Web APIs basecamp-content external change
Read: document.get_document · Asks approvalWrite: document.update_document · Always asksRead: upload.get_upload · Asks approvalWrite: upload.update_upload · Always asksRead: upload.list_upload_versions · Asks approvalRead: vault.get_vault · Asks approvalWrite: vault.update_vault · Always asksRead: vault.list_documents · Asks approvalWrite: vault.create_document · Always asksRead: vault.list_uploads · Asks approvalWrite: vault.create_upload · Always asksRead: vault.list_vaults · Asks approvalWrite: vault.create_vault · Always asks

Data it touches

SurfacesWeb APIs

About

Tags

pack:basecampbasecampdocumentsuploadsvaultsfilesapicomposition