- Issues: list with filters, read one, create and update (status, assignee, due date, custom attributes)
- Comments and attachments per issue: list, add, remove
- Project configuration reads: issue types and subtypes, custom attribute definitions and mappings, root-cause categories, the calling user's permissions
- 14 routes (9 read-only) on developer.api.autodesk.com, documented in the AI integration guide (llms.txt)
Autodesk APS Construction Issues Connector
Autodesk Platform Services' Issues API for Autodesk Construction Cloud and BIM 360 — list, create and update project issues, comments and attachments, issue types, custom attribute definitions and root-cause categories — registered in Apivom Atlas as 14 routes for construction-tech tenants that track field and design issues.
What you can do
Use cases
- Turn a customer complaint into a site issue — Create the issue in the customer's ACC project from your support or CRM record, with the right type, location and due date, and keep the two linked.
- Mirror issue status back to the office — Poll or sync issue status, assignee and comments so project managers and commercial teams see field progress without opening ACC.
- Quality and defect reporting — Read issues by type, root cause and status across projects to build defect statistics for handover and warranty reviews.
Issues are how Autodesk Construction Cloud and BIM 360 teams record defects, RFIs-in-waiting, safety observations and design questions against a project. The Issues API exposes that module: list a project's issues with filters and paging, read a single issue, create new ones and update status, assignee, due date or custom attributes; add and read comments; list, upload and delete attachments. Configuration endpoints return the issue types and subtypes, custom attribute definitions and their mappings, the root-cause categories and what the signed-in user may do in the project — the data an integration needs to create a valid issue. Access is three-legged with data:read and data:write scopes on a user who is a member of the project. Apivom Atlas catalogues all 14 routes, 9 of them 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 want issues to flow between ACC and their own ticketing or quality systems, and a product workflow is scoped per customer.
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.
Why do I need the configuration endpoints before creating an issue?
An issue must reference a valid issue type or subtype id and may carry custom attributes defined per project. Read issue-types, issue-attribute-definitions and the mappings first, cache them per project, and build the create payload from those ids.
Can the connector delete issues?
No. The Issues API has no delete endpoint for issues — they are closed by status. Attachments can be deleted; comments cannot.
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.