PLATFORM ACCESS · FOR DEVELOPERS & INTEGRATORS
Every specification and datasheet on SynC is structured, addressable data behind a REST API — read by your internal tools and your AI agents through integration keys scoped to exactly what each one needs.
Scoped keys · JSON export · Agent-ready
INTEGRATION KEY
quote-tool-prod
SCOPE
READ-ONLY
GET /api/projects/2841/datasheets?format=compact
Authorization: Bearer sync_k9…
HTTP/1.1 200 OK
X-RateLimit-Remaining: 29
{
"project": "Building 400",
"revision": 7,
"fingerprint": "f0d7ef311a02",
"datasheets": [ … ]
}PART 1 — GENERAL
Construction requirements are published as documents for humans — anything downstream starts with a person extracting the data by hand.
Most integrations demand an all-or-nothing credential: to read one project, a tool gets the keys to the whole account.
AI agents are already in every workflow, but the documents they need are unstructured pages they can only guess at.
A specification is a database. SynC treats it like one.
PART 2 — PRODUCTS
2.01
Issue keys with exactly the permissions a tool needs — read-only stays read-only, comment-only can’t read what it shouldn’t. Revoke any key at any time without touching the rest.
2.02
Projects, standards, datasheets, revisions, comments — every entity addressable by ID, every requirement by its clause address. The same data model the application itself runs on, with a published reference.
Read the API reference→2.03
Pull any project — or a single datasheet — as JSON: named fields, selected values, units, and the source revision’s fingerprint. Compact for machines, verbose when you need full provenance.
2.04
Request data as of any published revision, not just the latest. Quotes, bids, and analytics stay tied to the exact document set they were built against.
2.05
Point your agent at SynC and let it read specs, answer questions, and pull scope — under the same permission machinery as any user. No screen-scraping, no PDF parsing.
2.06
Rate limits scale with the account’s plan and are reported on standard X-RateLimit headers — write your retry logic once and stop guessing.
PART 3 — EXECUTION
STEP 01
Create an integration key from your account and grant it only the scopes the tool needs.
STEP 02
Read projects, standards, and datasheets as JSON, pinned to the published revision you name.
STEP 03
Push line-item responses back through the same API, so feedback lands on the exact requirement.
PART 4 — ON THE ROADMAP
PLANNED
Standards will carry decision-support metadata — why you’d pick one configuration over another — so an AI can help make the selection, not just read it back. It will feed the built-in chat and any AI you connect by integration key, which can already read and edit projects today.
ON ROADMAP
The keys, API, and structured export are launched — teams build against them today. Pre-built connectors for common configurators and ERPs come later, so not every integration starts from scratch.
Sign up free and issue your first key, or get in touch and we’ll walk your integration through together.