Public gateway

Obtain integration access from [email protected]. The Infinimesh developer console is at console.infinimesh.net. Send one credential per request. A request with both credentials returns EPX0007. Keep secret keys out of browser bundles, logs, and repositories.

Project identifiers

A project identifier is public. It does not authenticate an individual user. Configure the project’s allowed browser origins before use. The gateway does not expose GET /orders to project credentials. Use a backend for private order history. For browser POST requests, send x-project-id, Content-Type, and X-Infinity-Subject. Additional custom headers require gateway cross-origin policy support.

Your users

X-Infinity-Subject identifies the user within the authenticated tenant. Keep it stable across each quote, submission, and status workflow. Derive server-side subjects from an authenticated application session. Do not trust an arbitrary browser-supplied subject as proof of identity. Public chain observations are not private account data. A project identifier and known order identifier can expose that order’s status through permitted endpoints. Enforce application ownership before using an unscoped lookup for private account data.

Direct Infinity Hub service

The direct service supports account sessions, a configured delegating account, and a trusted proxy interface. Production backend delegation binds requests to an account and subject. Trusted proxy requests carry the configured proxy credential, organization, and subject. These headers are not public gateway credentials. Use the selected endpoint’s schema and deployment configuration. Do not send internal trusted-proxy credentials from a browser.