








































































































.webp)





















Fieldpoint is a field service management software for mid-market service contractors, supporting work orders, scheduling, mobile, project management, and integration with ERP and accounting.
Have any questions? We’re here to help You
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.
Makini monitors connection health continuously and provides multiple ways to detect reauthorization needs. The connection status endpoint returns the current state including whether reauthorization is required. Makini sends webhooks when connections enter a state requiring reauthorization, allowing proactive notification. API requests to a connection requiring reauthorization return specific error codes prompting reconnection. The Makini dashboard displays connection status across all customers. Best practice is to implement webhook listeners for connection status changes and proactively notify customers when reauthorization is needed, rather than waiting for operations to fail. Include clear instructions on how to reconnect in your notification.
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.
No. For M2M setup, both "Authorization Flow" and "Authorization Code Grant" should be unchecked. Only "Client Credentials (Machine To Machine) Grant" should be checked, along with the required scopes (Restlets and REST Web Services).
