ApivomApivom
Get Demo

Autodesk APS Object Storage Service (OSS) Connector

Autodesk Platform Services' Object Storage Service — app-owned buckets with retention policies, objects, signed S3 upload and download URLs, batch and multipart completion, copy and delete — registered in Apivom Atlas as 19 routes: the storage layer that feeds Model Derivative translations and the viewer.

What you can do

  • Buckets: create with transient, temporary or persistent retention, list, read details, delete
  • Objects: list and read details, batch signed S3 upload and download URLs, complete multipart uploads, copy, delete
  • Signed URLs let clients move large design files straight to and from Autodesk's storage without proxying bytes
  • 19 routes (7 read-only) on developer.api.autodesk.com, documented in the AI integration guide (llms.txt)

Use cases

  • Stage files for translation — Upload a model through signed S3 URLs into a transient bucket, hand its URN to Model Derivative and let the bucket expire on its own.
  • Persistent assets for a customer portal — Keep approved deliverables in a persistent bucket and issue time-limited signed download URLs from your portal instead of hosting the files yourself.

OSS is the application-owned storage of Autodesk Platform Services. An application creates buckets — named globally, with a retention policy of transient (24 hours), temporary (30 days) or persistent — and stores objects in them: design files to be translated by Model Derivative, outputs of Design Automation, or any binary a viewer-based application needs. Modern uploads and downloads use signed S3 URLs obtained in batches, with a completion call for multipart uploads, so the bytes travel directly between the client and Autodesk's storage. Objects can be copied to a new key and deleted; buckets can be inspected and removed. Access is two-legged: the bucket belongs to the application, not to a user. Apivom Atlas catalogues 19 routes, 7 read-only, with the APS credential contract and the AI integration guide (llms.txt), logging each call per tenant. No Apivom product workflow uses APS today; the connector is available to tenants that build viewer or translation pipelines, and a product workflow is scoped per customer.

Authentication

Your Autodesk Platform Services app (client id + secret from aps.autodesk.com) and the scopes this API needs. The caller obtains the OAuth2 v2 token — two-legged for app-owned data, three-legged for a user's hubs — and sends it as Bearer; Apivom Atlas forwards, logs and stores nothing.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

What do the retention policies mean?

Transient buckets delete objects after 24 hours, temporary after 30 days, persistent never — until you delete them. Pick per use: transient for translation staging, persistent for anything users must find again.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.