Sales integrations and inbound hooks

API keys let you pull data out of veedo. Integrations let other systems push sales in, so analytics and customers cover everything you sell — not only veedo vendors.

Where to set them up

Open Integrations in the dashboard. Each card has the URLs and secrets to paste into the other product. Free and Premium both include these connections.

Second Life Marketplace (ANS)

• veedo gives you a unique ANS URL shaped like https://veedo.store/api/v1/integrations/ans/{token} and a salt.
• In Marketplace merchant tools, set that URL as your Automated Notification System endpoint and use the salt veedo shows.
• Marketplace signs each notice with X-ANS-Verify-Hash (SHA-1 of the query string + salt). veedo verifies the hash before recording a purchase.
• Only Type=purchase notices are stored. Duplicates for the same transaction are ignored safely.

CasperVend and mdVendor

• Create a bridge from the Integrations card and paste the callback URL into CasperVend / mdVendor as directed on the card.
• Those systems keep taking payment and delivering; veedo only records the sale for analytics and your customer list.
• You can remove a bridge anytime — past sales stay in history.

Reading integration health from the API

With a read or orders key: GET /api/v1/stores/{storeId}/integrations returns which connections are active. Full setup still happens in the dashboard UI.

In-world scripts

Official veedo vendors and delivery servers talk to /api/v1/sl/… with pairing secrets after you pair them in the dashboard. That protocol — authentication, purchases, payment retries and delivery confirmations — is documented in In-world vendor API. It is for veedo (and partner) objects, not a general third-party write API. To automate reads, use API keys as in Connect to the veedo API.