Bulk Import API

introduction jomablue’s bulk import api is designed for external systems to add people records to jomablue people records are entities that attend events or experiences hosted in person, hybrid or virtually on jomablue people can be created or updated in bulk via a rest post request using a valid bearer token rate limit the number of api calls is based on your jomablue plan a soft default is 5 requests per minute and 250 person records per request (ie 1500 people records per minute) if this rate is exceeded the api will return 429 rate limit exceeded until the requests fall below 6 requests a minute we recommend having a minimum of 10 second wait between pushing batch requests of records to jomablue to stay within these limits there is a rate limit of 6 requests per minute due to this being a bulk insert api (as opposed to single record inserts) this still allows you to achieve around 1500 people per minute dates & times all date/times returned in our api's are in utc format (no timezone offsets are applied) noting that some endpoints do not return timestamps encoding for all requests url encoding (percent encoding) should be performed on the uri organisation uid (organisation uid) the organisation uid is a unique identifier of a person from an external system (eg crm’s) for example, if you have a person record in your salesforce crm that has indicated they are attending a jomablue event, the jomablue organisation uid would be the salesforce lead/contact id this allows your systems to keep track of people between systems as well as perform subsequent updates to particular people organisation uid’s are expected to be globally unique and therefore a single organisation uid may denote a person that has a relationship to multiple events in jomablue making updates to a person that is attending multiple jomablue events will update the persons details (first name, last name, job title, company, mobile and email) for all events noting that categories and custom fields are event specific request headers the client must include the following headers for each request content type application/json accept application/json when accessing a protected resource, the client must send an authorization header using the bearer schema authorization bearer {token} api url’s the general format for api requests is https //your organisation name jomablue com/import/api/v1/resource https //your organisation name jomablue com/import/api/v1/resource your organisaion name the organisation name as provided by jomablue api version the version of the api you are interacting with resource the resource you are interacting with a sample organisation named “acme” is used as an example throughout this document whitelisting to ensure our application or network firewalls don't misdiagnose your legitimate traffic, we ask for source ip's or identifying headers from your application to allow us to whitelist your traffic and prevent an interruption of service alternatively, we can provide you with custom http request header values to include in your requests