




















































































Coast is a mobile-first maintenance and operations app for SMB facilities, providing work orders, preventive maintenance, asset tracking, and team communication.
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.
Yes, customers can connect as many systems as needed. Each connection is independent with its own API token, allowing you to manage multiple ERP systems, CMMS platforms, or other integrations for a single customer. This is common in organizations with multiple subsidiaries, regional systems, or during migration periods when legacy and new systems run in parallel. Each connection consumes connection credits based on the system type and deployment model. There's no technical limit on the number of connections per customer. For customers using multiple instances of the same system (like regional SAP instances), each instance requires a separate connection with its own credentials and token.
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.
The integration record serves as the OAuth 2.0 application registration in NetSuite. It generates the Consumer Key and Consumer Secret (Client ID and Client Secret) that Makini uses to authenticate and connect to your NetSuite account. It also defines which authorization flows are permitted for the integration.
