Skip to main content

Azorus Integration

How to engage Azorus for the integration, what credentials to request, and where the field mapping is owned.

Azorus is Uni Compare's native-supported CRM. The integration uses an API credential and numeric field IDs for your Azorus tenant.

Azorus is fully supported by Uni Compare. The one difference from the other CRMs in this guide is setup: there is no self-service developer portal, so your Azorus account manager issues the credential and field IDs, and Uni Compare configures delivery. This page describes what to ask Azorus for and what to send us.

What we need from you

  • An Azorus API credential (an authentication header token) issued for your tenant. Your Azorus account manager generates this on Azorus's side because we cannot generate it ourselves.

  • The API base URL for your Azorus tenant (production), and the sandbox base URL if available. We use the sandbox for the pre-go-live test.

  • The numeric Azorus field IDs that correspond to each of the standard and custom Contact attributes in your tenant. Azorus identifies Contact fields by numeric IDs (for example, 19 for email, 27 for phone, 643 for course of interest). The IDs are different per tenant. Your account manager will provide the list when issuing the API credential.

How to engage Azorus

Contact your named Azorus account manager, or Azorus support via azorus.com/contact if you don't have one. Send a brief along these lines: "We are integrating with Uni Compare for inbound prospect lead delivery into our Azorus tenant. Please issue an API authentication header credential for this integration and confirm the numeric Azorus field IDs for the following Contact attributes: first name, last name, address, postcode, city, email, phone, study level, entry year, lead type, marketing consent, course of interest, enquiry text."

Azorus will typically respond with the API base URL, the credential, and the table of numeric field IDs.

Verify before sending

Before forwarding the credential, confirm the following:

  1. Credential received from Azorus. You have the API authentication header value from your Azorus account manager. This should be the actual header credential, not a username/password combination or a login URL.

  2. Base URL provided. You have the production API base URL (and sandbox base URL if your tenant has a sandbox). The URL is specific to your tenant. It is not a generic api.azorus.com address.

  3. Field ID table received. Azorus has provided the table mapping the listed Contact attributes (email, phone, study level, etc.) to their numeric field IDs in your tenant. Without this table we cannot configure the field mapping.

  4. Channel. Generate a one-time encrypted link using our secrets page with the API credential, then email the link to your Uni Compare contact. The base URL and field-ID table can come via the support chat (they're configuration metadata, not credentials).

Important: Never paste credentials into a web chat, plain email, or any unencrypted attachment.

Field mapping

We create Contact records in Azorus, deduplicated by email. If a contact with the same email already exists, we update it; otherwise we create a new one.

Azorus identifies Contact fields by numeric ID rather than by name, so each Uni Compare field is written to the Azorus field ID you (or your account manager) nominate at onboarding.

The mapping below shows what we send. Your tenant-specific numeric IDs are agreed during setup:

  • First name and last name → Azorus field IDs you nominate

  • Email → Azorus field ID you nominate

  • Phone (where given) → Azorus field ID you nominate

  • Postcode → Azorus field ID you nominate

  • Address (where given) → Azorus field ID you nominate

  • Study Level (undergraduate or postgraduate) → Azorus field ID you nominate. Note: we map our values (undergrad, postgrad, phd) onto Azorus's expected text labels (Undergraduate, Postgraduate Taught, Postgraduate Research (PhD)). Confirm with your account manager that those labels match what Azorus expects for the level field in your tenant

  • Start Year → Azorus field ID you nominate

  • Subject Area (where given) → Azorus field ID you nominate

  • Free-text enquiry message (where given) → Azorus field ID you nominate

  • Lead type → Azorus field ID you nominate

  • Marketing consent flag → Azorus field ID you nominate (boolean field)

  • Uni Compare lead identifier → Azorus field ID you nominate (for traceability)

Frequently asked questions

Why do we have to engage Azorus directly? Can Uni Compare do it for us?

Azorus credentials are tenant-scoped and Azorus issues them only to the tenant owner (you). We cannot generate them on your behalf. However, Uni Compare can join the conversation with Azorus on a three-way call if it helps move things along. Request this via the support chat.

Azorus already pushes leads from another source into our CRM. Does that affect this?

It might. If Azorus is configured to forward inbound leads to another system on your side (a Salesforce or HubSpot, say), we should discuss whether to deliver to Azorus or directly to that downstream system. Open the support chat and we will work it out.

Is there a published Azorus API document we can read?

Azorus does not publish public API documentation. Your account manager will share what's relevant to your tenant, and we configure the integration from what they provide.

Useful links

  • Azorus website — the official Azorus website, including their product pages and contact details for sales and support.

  • Contact Azorus — use this if you do not have a named account manager and need to request API access.

Related Articles
Did this answer your question?