Documentation menu
Authentication
How PartGrid separates browser-facing embed interfaces from authenticated account and server-side operations.
Authentication model
PartGrid uses separate trust boundaries for customer-facing embeds, authenticated dashboard workflows, and approved server-to-server integrations. Browser applications should use only the public interfaces documented for embeds and storefront experiences.
Account and server APIs
Dashboard and account APIs are not offered as a general public interface. Use the supported PartGrid application workflows unless your organization has received a documented integration agreement, scoped credentials, and environment details directly from PartGrid.
Public embed interfaces
Public embed and storefront interfaces expose only the information needed to render a published customer experience or submit a supported customer action. They are not management APIs and should not be used to automate dashboard operations.
Operational security
Keep publishing, credential rotation, signing secrets, and integration access inside the supported PartGrid workflows and server-side environments.
- Publish only schematics and collections intended for customer access.
- Rotate integration credentials when storefront or team access changes.
- Keep signing secrets and server credentials outside frontend bundles and source control.
- Use the official embed or integration flow instead of calling internal application routes.