The owner uses Read API and events at the real site to delegate read access and set up signed event destinations. These connections do not post stock movements. Changes need recent Accounts verification, and creating or expanding integrations also needs the applicable integration entitlement and current site authority.
Issue the smallest useful read credential
In Create a scoped read credential, enter Name for the receiving system and select only the read scopes it needs. At least one scope is required. The offered scopes cover items, lots, locations, pools, availability, demands, reservations, history and events.
Enter an explicit future Expiry in UTC, if required, using the form's UTC example format, and a whole Requests per minute value from 1 to 600. Although the expiry label says 'if required' and the form accepts a wider rate, recording requires an expiry within the next 365 days and a rate no higher than 600. Use those bounds; do not leave expiry empty.
Choose Create a read credential and copy New read credential to the authorised receiving system while it is displayed. Closing or reloading loses that value. Hide this value removes it from view. The retained list shows metadata, including scopes, expiry and status, rather than the secret. Never use this credential as an operator sign-in.
To withdraw access, find the exact record under Read credentials and choose Revoke this credential. Check that its status is revoked. Retained metadata remains available for review.
Create or change a signed destination
Arrange the public HTTPS receiving endpoint and the receiving system's signature handling before enabling it. In Prepare an event destination, enter Public HTTPS receiving endpoint and set Enable this destination after its receiving system is ready deliberately, then choose Create this event destination.
Copy the displayed Webhook signing secret (base64) and signing key ID to the authorised receiver. The receiver uses the decoded secret bytes for signature verification. The secret is shown once. Creation establishes a boundary for future events; it does not automatically send the site's entire earlier history.
For a change, choose Load these destination details, inspect the endpoint and enable checkbox, then use Apply the edited details to this destination on that exact row. To disable delivery, clear the enable checkbox and apply it. Select the signing-secret rotation checkbox only when the receiving system is ready to replace its verification secret, and preserve the newly displayed value.
A changed destination is a new reviewed revision. A retained delivery belongs to its recorded destination revision, so editing the endpoint is not a way to redirect an old event silently. A restored registration can need fresh setup and reconciliation; follow recovery and closure and ask support when the current destination cannot be used.
Review delivery before requesting a replay
Read Delivery status, including the state, attempts, reason, latest HTTP status and next-attempt time where shown. A pending or leased delivery is distinct from one requiring a person. Coordinate with the receiver before replaying an event that it may already have processed; duplicate events retain their original identity.
For a replayable parked, held, retained or retry record, choose Select this retained delivery, check Retained delivery ID, enter Reviewed reason for replay and use Request reviewed replay of this retained event. The current destination and authority must still permit that retained delivery. The result schedules it as pending; it is not proof of acknowledgement by the receiver.
Resolve an unconfirmed integration change
This page has its own recovery controls. If it says the change has no confirmed result, do not submit it again. Use Reload integration metadata, then review the newly retained key or destination metadata. Revoke an uncertain new credential or disable an uncertain destination as appropriate before creating a replacement. A lost one-time secret cannot be recovered by assuming the request failed.
Only after that review, use I have reviewed or revoked the uncertain records. This clears the page's warning without resending the old request. Retain the receiving-system name, record ID, destination revision, time and evidence checked for the next owner. It does not settle a separate unconfirmed stock movement.