aXcelerate Sync

If your RTO runs aXcelerate, you can sync contacts straight into a Master List — students, trainers, or both. Enrolment data comes with them, so you can scope a list to a single qualification and issue cards to exactly that cohort. aXcelerate is the only connector that also works outbound: once a photo is approved in CaptrID, it can be written back onto the contact record in aXcelerate, so your student management system ends up with the photograph too. aXcelerate connections live under Directory Integrations, alongside Microsoft Entra ID, Airtable and Wonde.

​

Step 1: Add the connection

1. Go to Directory Integrations → Add Connection → aXcelerate
2. Enter your API credentials from aXcelerate

Connections are shared across your CaptrID organisation — re-use an existing one rather than adding it again for each Master List. Use Test on the connection card to confirm the credentials work before building a sync on top of them.

​

Step 2: Choose who the list syncs

This is the decision that shapes everything after it.

​

Narrowing students by enrolment status

For a Students list, pick which enrolments count:

​

Narrowing by qualification, campus or faculty

Optionally narrow further — add a qualification by code, or a campus or faculty by name. Leave them empty to include everyone in scope.

​

Step 3: Choose the unique identifier

Every Master List needs one field that identifies a person and never changes. Contact ID is always the safe choice — it is immutable and always present. Student ID is only reliable if your RTO fills it in consistently; the wizard shows “No value seen in the sample of contacts probed” when it does not.

​

Step 4: Map your fields

Standard fields are expanded by default. Import brings unmapped aXcelerate fields into your Master List schema in one step — new fields are added to the schema and become available everywhere in CaptrID.

​

Step 5: Photos in

Turn on photo sync and CaptrID pulls each contact’s photo from aXcelerate and re-hosts it in Australian storage. As with other connectors, choose whether it only fills gaps or overwrites on every sync. If you run photo days, use only-if-missing so an approved capture is not replaced by an older file from the SMS.

​

Step 6: Photos back out to aXcelerate

The part no other connector does: CaptrID can write an approved photo back onto the aXcelerate contact record, so your SMS holds the same photograph as the card. This runs manually, on request, rather than automatically on approval.

​

Step 7: Schedule it

Set a cadence to keep the list current:

• Manual only (no scheduled sync)
• Every 6 hours
• Every 12 hours
• Every 24 hours

​

A note on what you can see

CaptrID reads only what your aXcelerate API credentials permit. If a field you expect is missing from the mapping step, the permissions on the credentials are the first place to look.

​

Related