Integration Overview

Current Evidence

Reported beta, not independently verified: The supplied handoff describes local public RFQ intake at /rfq/{manufacturerSlug} and a manufacturer workspace. A public browser page is not evidence of an integration API.

Planned: Embedded portals, API access, and webhooks are future scope. No usable integration contract is established by the supplied evidence.

Choose a Safe Approach Today

If you want to direct buyers to intake, first obtain and confirm your manufacturer-specific public link through your existing beta onboarding contact. Consider whether linking to that page meets your immediate need without assuming it can be embedded or automated.

Before planning automation, describe the business outcome you need: what information should move, when it should move, and who should receive it. Avoid building against inferred network calls or undocumented behavior, which are not a supported public contract.

Plan Without Assuming Availability

Read the boundaries for an embedded portal, API, and webhooks.

Verification gaps: There are no verified public endpoints, credentials, payload schemas, event names, delivery guarantees, or integration availability dates in this evidence. Do not share production credentials or sensitive drawings as part of an unconfirmed integration test.

See the roadmap for broader planned capabilities. It is not a delivery commitment.