Developer connection
Build around the data your business needs.
Start with the information your other system needs. Retail's integration settings include named API keys with separate read scopes for products, inventory, sales and reports.
Define whether your project needs catalog details, inventory, completed sales or daily reporting. Retail’s read scopes separate those areas. Request documentation for the records you need and confirm field meanings, location boundaries and update timing before writing a receiving integration.
Use a recognizable name for each API connection and record who maintains it. Review how keys are issued, stored, rotated and revoked with your technical team. Keep credentials on the appropriate server and out of shared documents or general support messages.
Compare a small sample with the Retail source records, including products with variants and sales with refunds where relevant. Read access does not authorize charging customers, issuing refunds or editing completed sales. Discuss any additional operation and its supported interface separately with Taply.
Bring your idea, your expertise and the workflow you want to improve.
Become an integration partner