NetworkAssist360 Integration API

Search the N360 provider network and read provider records from your own system, with exactly the engine, scope and ranking a coordinator sees. Read-only, key-authenticated, versioned.

What N360 is

NetworkAssist360 is the provider network platform assistance companies use to find, verify and reach medical, security and logistics providers anywhere in the world. This API gives your case management system or portal the same provider search a coordinator uses, so a provider found by your system is the provider N360 would have shown.

Get a key

Keys are issued by the N360 team on the platform's Integrations screen and shown once. A sandbox key starts n360_test_ and works against the seed network; a live key starts n360_live_. Ask your N360 contact for a sandbox key to begin. Keep it server-side: a key in browser code is a published key.

Your first call

Hospitals in Kenya within 50 km of Nairobi, five to a page. Replace the key and run it as printed:

curl -H "Authorization: Bearer n360_test_YOUR_KEY_HERE" \
  "https://api.networkassist360.co.uk/v1/providers/search?country=KE&lat=-1.2921&lng=36.8219&radiusKm=50&pageSize=5"

You get total, page, pageSize and results - each result with id, name, categoryPath, address, location, distanceKm, switchboard, languages, accessMethods, tier, lastVerifiedUtc, localTimeZone, openingHoursText and hasAlert. Then read one record:

curl -H "Authorization: Bearer n360_test_YOUR_KEY_HERE" \
  "https://api.networkassist360.co.uk/v1/providers/12345"

Filter ids - categories, specialisms, languages, access methods, countries with their ISO codes - come from /v1/lookups/{name}, so your form never hardcodes our vocabulary. The location briefs for a country are at /v1/countries/{iso2}/notes.

Authentication

Every call to /v1/ sends Authorization: Bearer <key>. Nothing else is accepted: not a query string, not a cookie. Keys are stored only as a hash on our side. A key can be revoked at any time and fails on the very next call. Each integration is scoped to the networks it may see and the endpoints it may call; a provider outside your scope does not exist as far as the API is concerned.

Errors

Errors are application/problem+json (RFC 7807) with a stable code:

StatuscodeMeaning
401key_invalidNo key, or one we do not recognise.
401key_revokedThe key or its integration has been revoked.
401key_expiredThe integration's access has expired.
403scope_deniedThe key is not enabled for this endpoint.
429rate_limitedOver the per-minute limit; Retry-After says how long to wait.
404not_foundUnknown id, lookup or country - or a provider outside your scope.
400validation_failedA parameter is wrong; errors names each field.
{ "type": "https://api.networkassist360.co.uk/docs/#errors", "title": "A parameter is wrong", "status": 400,
  "detail": "One or more parameters are wrong - see errors.", "instance": "/v1/providers/search",
  "code": "validation_failed", "errors": { "radiusKm": "radiusKm is above 0 and at most 500." } }

Rate limits

Each key has a fixed window per minute - 60 calls on a sandbox key, 600 on a live key unless agreed otherwise. Every answer carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset (seconds to the next window). The call over the limit gets 429 with Retry-After. Pages are at most 50 results; ask for the next page rather than a bigger one.

Versioning

The path carries the version: /v1/. Within v1 changes are additive only - new optional fields, new endpoints, new lookups. Anything breaking becomes /v2/, with v1 kept running for a stated period. Every timestamp is UTC ISO 8601 and ends in Z.

What the API deliberately does not return

Reference

Generated from the live OpenAPI document: /openapi/v1.json (download it for your client generator). Expand an operation for its parameters and response shape.

Loading the reference...