Last modified at 2022.03.22
HOW TO ENABLE ACCESS TO 3RD-PARTY API FOR DEVELOPERS
Access to 3rd-party API is managed by PACE Sport admins. If you want access to the API, please contact us support@pace.sport.
When API access is enabled, developers can find the button Create new API credentials at their porfile page in PACE.
When requesting credentials, email is sent to the email address of that PACE account. There will be:
- API ID that will link to the developer’s account and will not change. It looks like: DQSUCBWE1Y6TM1PYR7JP77AGP9682JHC
- API Secret that developers should securely store. It looks like: ULANdvF8Y20cdtfrcqIAbhSZle445VZrfjREOM6+K50=
We don’t store the Secrets, so if developer loses it, they can request new API Secret at any time by clicking the button Create new API credentials. Old Secret will be changed to a new one. API ID will not change.
HOW TO GET ACCESS TO THE EVENT’S PARTICIPANT LIST
Event Organizers can give developers access to all participants at their events. Organizer can find it on Participant Management page by click on API export settings.
On pop-up Event Organizer can allow access to the events participant list and generate access code.
Event Organizer will share this access code to developers. If the organizer suppose that access code is stolen, it can be regenerated and shared to developers again.
HOW TO EXPORT PARTICIPANT LIST
Request example
POST https://pace.sport/api/events/getParticipants
content-type: application/json
{
"apiId": "DQSUCBWE1Y6TM1PYR7JP77AGP9682JHC",
"apiSecret": "ULANdvF8Y20cdtfrcqIAbhSZle445VZrfjREOM6+K50=",
"accessCode": "VZ5B066Z",
"eventSlug": "event-with-participants",
"language": "en",
"updatedAfter": "2022-02-01",
"sortDirection": "desc"
}
Explanations
Here are 4 required fields: apiId, apiSecret, accessCode and eventSlug:
- apiId and apiSecret developers received on their email and can regenerate
- accessCode provided by Event Organizer
- eventSlug is the last part of the URL of the event. For example if the URL of event is https://pace.sport/events/pace-triathlon-espoo, eventSlug is pace-triathlon-espoo.
Optional fields:
- language – can be en (by default) or fi. This enables to translate field keys from JSON responses. We provide field keys in human readable format, that can be mapped to DB-related format by the developer on post-receiving process. For ex. “Event name” for en or “Tapahtuma” for fi. Some of the fields does’t have translations, for example custom fields that Event Organizer included to registration form.
- updatedAfter takes the datetime in RFC 3339 format (2022-02-01, 2022-02-01 00:00:00.000Z, 2022-02-01T00:00:00.000Z so on). This can be used to filter only recently updated participant information.
- sortDirection can be desc (by default) or asc. It sorts the list of participants by Updated at field.
Response example
[
{
"Event name": "Event with participants",
"Distance": "Marathon",
"Group": "General",
"Payment": 30,
"Currency": "EUR",
"License validation": "Yes",
"Order date": "2022-03-15T12:16:29.617Z",
"Order number": "KI759205",
"Status": "succeeded",
"Updated at": "2022-03-14T13:50:46.873Z"
"First name": "AthleteName",
"Last name": "AthleteSurname",
"Email": "athlete@gmail.com",
"Birthdate": "2021-06-10",
"Gender": "female",
"Country": "FI",
"Phone": "+358412345678",
"Nationality": "FI",
"Sport ID": "0123456"
},
{
"Event name": "Event with participants",
"Distance": "Half Marathon",
"Group": "Elite",
"Payment": 20,
"Currency": "EUR",
"License validation": "Yes",
"Order date": "2022-03-14T13:50:46.873Z",
"Order number": "HB389788",
"Status": "succeeded",
"Updated at": "2022-03-14T13:50:46.873Z"
"First name": "First",
"Last name": "Last",
"Email": "sporty@gmail.com",
"Birthdate": "2001-06-10",
"Gender": "male",
"Country": "FI",
"Phone": "+358412345679",
"Nationality": "FI",
"Sport ID": "1234567"
}
]