




















































































Agilysys WMS, also known as Eatec, provides warehouse and inventory management for hospitality, food service, and retail operations with capabilities for receiving, stockroom, and recipe management.
Have any questions? We’re here to help You
API tokens must be stored securely and should never be exposed on the client side or in public repositories. Store tokens in secure environment variables or dedicated secrets management systems like AWS Secrets Manager, HashiCorp Vault, or Azure Key Vault. Never hardcode tokens in application code or commit them to version control. Implement proper access controls so only authorized services can access stored tokens. For production environments, use separate tokens from development/testing environments. Rotate tokens periodically and immediately revoke tokens if you suspect they've been compromised. Makini tokens provide access to customer data, so treat them with the same security standards you'd apply to database credentials.
All Makini webhooks include a signature header for verification. The signature is an HMAC hash of the webhook payload using your webhook secret as the key. To verify a webhook, compute the HMAC using your secret and compare it to the signature header using constant-time comparison to avoid timing attacks. Never process webhook data without verification, as this could expose your system to forged requests. Your webhook secret is provided when you configure webhooks and should be stored securely. Webhook verification ensures that only legitimate requests from Makini are processed by your application.
The integration role must have the following essential permissions:
• Log in using OAuth 2.0 Access Tokens (Full level)
• REST Web Services (Full level)
Additionally, you should add specific permissions based on your integration needs, such as permissions for Transactions, Lists, Reports, or Custom Records.
You have two options:
• Option A: Upload the Makini public certificate (available in the Resources section of the guide)
• Option B: Generate your own self-signed certificate using OpenSSL and upload the public key to NetSuite
