Skip to content

Data Management Commands

Browse and manage BIM 360/ACC hubs, projects, folders, and items. These commands require 3-legged OAuth authentication.

Commands

Hub Commands

raps hub list

List all accessible hubs.

Usage: 

raps hub list

Example: 

$ raps hub list
Fetching hubs (requires 3-legged auth)...

Hubs:
────────────────────────────────────────────────────────────────────────────────
Hub Name                                        Type           Region
────────────────────────────────────────────────────────────────────────────────
My Company Hub                                  BIM 360        US
  ID: b.abc123xyz
ACC Project Hub                                 ACC            US
  ID: b.def456uvw
────────────────────────────────────────────────────────────────────────────────

Requirements: - 3-legged OAuth authentication (raps auth login)

raps hub info

Get detailed information about a hub.

Usage: 

raps hub info <hub-id>

Example: 

$ raps hub info b.abc123xyz
Fetching hub details...

Hub Details
────────────────────────────────────────────────────────────
  Name: My Company Hub
  ID: b.abc123xyz
  Type: hub
  Region: US
  Extension: BIM 360
────────────────────────────────────────────────────────────

Use 'raps project list <hub-id>' to see projects

Requirements: - 3-legged OAuth authentication

Project Commands

raps project list

List projects in a hub.

Usage: 

raps project list <hub-id>

Example: 

$ raps project list b.abc123xyz
Fetching projects...

Projects:
────────────────────────────────────────────────────────────────────────────────
Project Name                                    Type           Status
────────────────────────────────────────────────────────────────────────────────
Office Building Project                         ACC            active
  ID: b.project123
Warehouse Renovation                            BIM 360        active
  ID: b.project456
────────────────────────────────────────────────────────────────────────────────

Requirements: - 3-legged OAuth authentication

Folder Commands

raps folder list

List contents of a folder.

Usage: 

raps folder list <project-id> <folder-id>

Example: 

$ raps folder list b.project123 urn:adsk.wiprod:fs.folder:co.abc123xyz
Fetching folder contents...

Folder Contents:
────────────────────────────────────────────────────────────────────────────────
Name                                            Type           Size
────────────────────────────────────────────────────────────────────────────────
Models                                          folder         -
  ID: urn:adsk.wiprod:fs.folder:co.def456uvw
Documents                                       folder         -
  ID: urn:adsk.wiprod:fs.folder:co.ghi789rst
building.dwg                                    item           2.45 MB
  ID: urn:adsk.wiprod:fs.file:co.jkl012mno
────────────────────────────────────────────────────────────────────────────────

Requirements: - 3-legged OAuth authentication

raps folder create

Create a new folder.

Usage: 

raps folder create <project-id> <parent-folder-id> <folder-name>

Example: 

$ raps folder create b.project123 urn:adsk.wiprod:fs.folder:co.abc123xyz "New Folder"
Creating folder...
✓ Folder created successfully!
  Name: New Folder
  ID: urn:adsk.wiprod:fs.folder:co.xyz789abc

Requirements: - 3-legged OAuth authentication - data:write scope

Item Commands

raps item list

List items in a folder.

Usage: 

raps item list <project-id> <folder-id>

Example: 

$ raps item list b.project123 urn:adsk.wiprod:fs.folder:co.abc123xyz
Fetching items...

Items:
────────────────────────────────────────────────────────────────────────────────
Name                                            Type           Size        Version
────────────────────────────────────────────────────────────────────────────────
building.dwg                                    file           2.45 MB     v1
floorplan.pdf                                   file           1.23 MB     v2
────────────────────────────────────────────────────────────────────────────────

Requirements: - 3-legged OAuth authentication

raps item versions

View versions of an item.

Usage: 

raps item versions <project-id> <item-id>

Example: 

$ raps item versions b.project123 urn:adsk.wiprod:fs.file:co.abc123xyz
Fetching versions...

Versions:
────────────────────────────────────────────────────────────────────────────────
Version  Date                    Modified By          Size
────────────────────────────────────────────────────────────────────────────────
v2       2024-01-15 10:30:00     john.doe@example.com  2.45 MB
v1       2024-01-10 14:20:00     jane.smith@example.com 2.12 MB
────────────────────────────────────────────────────────────────────────────────

Requirements: - 3-legged OAuth authentication

raps item bind

Bind an OSS object to an ACC/BIM 360 project folder, creating a linked item.

Usage: 

raps item bind <project-id> <folder-id> [--object-id OBJECT_ID] [--file-name NAME] [--version-type TYPE]

Arguments: - project-id: Project ID (with "b." prefix) - folder-id: Target folder ID/URN

Options: - --object-id, -o: OSS object ID/URN to bind - --file-name, -f: Display name for the item in ACC - --version-type, -t: Version type (file, folder, attachment)

Example: 

$ raps item bind b.project123 urn:adsk.wiprod:fs.folder:co.abc --object-id urn:adsk.objects:os.object:my-bucket/model.dwg --file-name "Building Model.dwg"
Binding OSS object to ACC folder...
✓ Item created!
  Item ID: urn:adsk.wiprod:fs.file:co.xyz789
  Name: Building Model.dwg
  Folder: Plans/Models
  Version: v1

Interactive Example: 

$ raps item bind b.project123 urn:adsk.wiprod:fs.folder:co.abc
Enter OSS object ID: urn:adsk.objects:os.object:my-bucket/model.dwg
Enter display name (default: model.dwg): Building Model.dwg
Binding OSS object to ACC folder...
✓ Item created!

Workflow: Upload and Bind

Upload a file to OSS and bind it to an ACC project:

# 1. Upload to OSS
$ raps object upload my-bucket model.dwg
# Note the object ID: urn:adsk.objects:os.object:my-bucket/model.dwg

# 2. Bind to ACC folder
$ raps item bind b.project123 urn:adsk.wiprod:fs.folder:co.abc \
    --object-id urn:adsk.objects:os.object:my-bucket/model.dwg \
    --file-name "Building Model.dwg"

Use Cases: - Link externally uploaded files to ACC projects - Create items from Design Automation outputs - Migrate files from OSS to ACC while preserving metadata

Requirements: - 3-legged OAuth authentication - Write permissions on target folder - OSS object must exist and be accessible

Common Workflows

Browse a Project Structure

# 1. List hubs
raps hub list

# 2. List projects in a hub
raps project list b.abc123xyz

# 3. List folder contents
raps folder list b.project123 urn:adsk.wiprod:fs.folder:co.abc123xyz

# 4. View item versions
raps item versions b.project123 urn:adsk.wiprod:fs.file:co.def456uvw

Create a Folder Structure

# 1. Get root folder ID (usually from project info)
# 2. Create a folder
raps folder create b.project123 urn:adsk.wiprod:fs.folder:co.root "Models"

# 3. Create subfolder
raps folder create b.project123 urn:adsk.wiprod:fs.folder:co.models "2024"

Project ID Format

Important: When using Data Management commands, use the project ID without the "b." prefix that's used internally.

  • Correct: b.project123 (as shown in raps project list)
  • Incorrect: project123 (missing "b." prefix)

However, for Issues API commands, use the project ID without the "b." prefix: - Correct for Issues: project123 - Incorrect for Issues: b.project123

Hub Types

  • BIM 360 - Autodesk BIM 360 projects
  • ACC - Autodesk Construction Cloud projects
  • A360 - Autodesk A360 projects
  • Fusion - Autodesk Fusion projects

Permissions

Different operations require different scopes:

  • Read operations (list, info, versions): data:read
  • Write operations (create): data:write or data:create

Ensure you have the appropriate scopes when logging in: 

raps auth login
# Select the required scopes