Web Services and API Integration

Some business problems come down to two systems that do not talk to each other. The CRM does not update accounting, website orders are re-keyed into operations, vendor price files arrive by email, and reports depend on someone's manual export. IKRC builds the web services and integration layers that move that data automatically.

Integration work we handle

• REST and SOAP web service integrations with vendors and SaaS platforms
• SaaS-to-SaaS and SaaS-to-internal-system workflows
• Database synchronization and scheduled data movement
• Error handling, retries, logging and reconciliation reports
• Credential storage, token refresh handling and alerts when a refresh fails

Why integrations stop working months later

Authentication is one possible cause. With the Microsoft identity platform, refresh tokens last 90 days by default in most scenarios, but only 24 hours for single-page applications, and they can be revoked earlier, for example after a password reset or an admin action. That applies to integrations acting for a user; a background service using the client credentials flow is never issued a refresh token and requests new access tokens with its own secret or certificate, which has its own expiry to track. An integration that stores one refresh token and never handles a failed refresh can pass testing and later stop, and without monitoring nobody is told. IKRC builds token handling that stores the newest token after each refresh, alerts someone when a refresh fails, and gives support staff a way to see which records were held back.

For API design on your own platform, see API Development.