Skip to main content

Getting Started

Welcome to the Assist Insurances Developer Portal. This guide will help you get up and running with our APIs in minutes.

Overview​

Assist Insurances provides two API environments:

  • Production API (api.assistinsurances.ie) - For Insly integration with quote pricing and lookups
  • Test API (apim-assist-test-ne.azure-api.net) - For Applied Systems integration with full quote lifecycle

Both APIs use OAuth 2.0 client credentials flow for authentication.

Prerequisites​

Before you begin, you'll need:

  1. API credentials (client ID and client secret)
  2. A development environment with support for HTTP requests
  3. Basic understanding of REST APIs and OAuth 2.0
Get API Credentials

Contact neil.reilly@assistinsurances.ie to obtain your API credentials.

Quick Start: 5-Minute Integration​

Step 1: Get an Access Token​

Choose your preferred method:

curl -X POST "https://api.assistinsurances.ie/auth/token" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "client_id=YOUR_CLIENT_ID" \
-d "client_secret=YOUR_CLIENT_SECRET" \
-d "scope=api://1c15f5fa-f434-401b-b4ec-ab3ea75d48bb/assist-api-gateway/.default" \
-d "grant_type=client_credentials"

Response:

{
"access_token": "eyJ0eXAiOiJKV1QiLCJhbGc...",
"token_type": "Bearer",
"expires_in": 3599
}
Token Expiry

Access tokens are valid for 1 hour (3599 seconds). Implement token caching and refresh logic in your application.

Step 2: Make Your First API Call​

curl -X POST "https://api.assistinsurances.ie/priceQuote" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"data": {
"in_policy.dateInception": "2025-10-02T00:00:00+01:00",
"in_customer.dateOfBirth": "1987-09-18",
"in_dts.raterCover": "Comprehensive"
}
}'

Response:

{
"rater.Comp.GrossPrem": 372.5,
"rater.Comp.PolFee": 60.0,
"rater.Comp.PremAfterPolFee": 426.0
}

Next Steps​

Now that you've made your first API call, explore:

Rate Limits​

All APIs have a rate limit of 100 requests per minute per IP address. Rate limit information is included in response headers:

  • X-RateLimit-Limit - Maximum requests per minute
  • X-RateLimit-Remaining - Remaining requests in current window
  • X-RateLimit-Reset - Unix timestamp when the rate limit resets
Rate Limit Exceeded

If you exceed the rate limit, you'll receive a 429 Too Many Requests response. Implement exponential backoff in your application.

Need Help?​

Best Practices​

  1. Token Management

    • Cache access tokens and reuse them until expiry
    • Implement automatic token refresh before expiry
    • Never expose credentials in client-side code
  2. Error Handling

    • Always check HTTP status codes
    • Implement retry logic with exponential backoff
    • Log errors for debugging
  3. Performance

    • Use connection pooling for HTTP clients
    • Implement request timeouts (recommended: 30 seconds)
    • Cache lookup results where appropriate
  4. Security

    • Store credentials securely (use environment variables or secret management)
    • Use HTTPS for all API calls
    • Rotate credentials periodically