BigMarker

Authentication & Authorization

Credentials

• BigMarker connects via API key.

• API key is set with the HTTP API-KEY request header.

• API keys can be requested in the BigMarker API&White Label settings (see the DataGrail Help Docs).

• Publicly exposing your API keys can allow unauthorized access to the BigMarker API endpoints, and your BigMarker data by a third party. DataGrail stores your API keys encrypted and protected.

Permissions

No special scopes required and used to connect API with related credentials.

Base URL

Base URL consists of the API URL and API version:

• https://www.bigmarker.com/api/{API_VERSION}

Example of BASE URL:

• https://www.bigmarker.com/api/v1

Endpoints Utilized

DataGrail uses the following endpoint to validate that connection is good based on a successful response:

• GET {BASE_URL}/channels

DataGrail does not use this endpoint for any other purpose nor uses any of the data returned.

Version

BigMarker integration currently supports API Version 1.0 (v1).

Limits

DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

Access

For an access request, DataGrail will take the following actions:

• Get list of conferences

• Get list of channels

• Get list of channel registrants

• Get list of channel subscribers

• Get list of conference attendees

• Get all presenters of conference

• Get list of webinar attendees

• Get list of on demand attendees

• Get a chat transcript of the conference

• Get a question transcript of the conference

• For all objects found, DataGrail will return all available fields. You can edit which objects and fields you want to provide to the Data Subject via our Portal Requests.

Endpoints Utilized

• GET {BASE_URL}/conferences

• GET {BASE_URL}/channels

• {BASE_URL}/conferences/registrations/channel/channel_id

• {BASE_URL}/channels/channel_id/subscribers

• {BASE_URL}/conferences/conference_id/attendees

• {BASE_URL}/conferences/conference_id/presenters

• {BASE_URL}/reporting/conferences/live_attendees/conference_id

• {BASE_URL}/reporting/conferences/on_demand_attendees/conference_id

• {BASE_URL}/reporting/conferences/chat_transcript/conference_id

• {BASE_URL}/reporting/conferences/q_and_a_transcript/conference_id

Deletion

For a deletion request, DataGrail will take the following actions:

• Run all data access steps to find objects that can be deleted (see Access section above). You can select which found objects you want to delete via our Portal Requests.

• Anonymize (Update) presenter in a conference

• Delete a member from a channel

DataGrail also supports the Direct Contact Deletion workflow for BigMarker integration.

Endpoints Utilized

• PUT {BASE_URL}/presenters/presenter_id

• DELETE {BASE_URL}/channels/channel_id/delete_member