Do you have your own CRM? No worries! Our API integration lets you import all lead information right into your CRM. So that you have seamless integration with your existing workflows. Our API's can be integrated with any CRM including Salesforce, Pipedrive, Zoho, etc.

10times supports both Push and Pull API.

Let's see how this works.

Push API

This process will be used when you want to transfer data from 10times to your own CRM software. To do so, kindly follow the steps below:

Step 1: Select the event from oDash, for which you want to use API integration.

(Refer to the below image.)

Step 2: Open your Dashboard and scroll down you will find API integration under Tool & Widget.

Step 3:

Now here you can paste your API highlighted red in the below image. You can also Run a sample test as shown in the image.

Use Case:

Suppose an organizer has 2 events on 10times and he/she wants to segregate the leads for both of them. So we may add their unique event IDs in the Custom Values and their names in the field Custom Variables respectively, as shown in the below screenshot.

You can also choose the type of leads (Visitor, Exhibitor or Both) from the drop-down and at last, click on the save settings option.

Now, the data from 10times will be pushed to your CRM.

Please Note: This feature can also be used in a case where we want to segregate leads generated from two different platforms, say, 10times and Facebook.

PULL API

This process will be used when we want to import the data/ leads from the third party software to 10times software (Partner Dashboard)

REQUEST METHOD

POST

END POINT

https://api.10times.com/v1/register

PAYLOAD

Parameter

Description

Data Type

key

[Mandatory] Provided By 10times

string

event

[Mandatory] Event to be registered with

integer

channel

[Mandatory] Channel of payment

string

attendee[0][‘name]

[Mandatory] User’s name

string

attendee[0][‘email’]

[Mandatory] User’s Email

string

(Format:<email>)

attendee[0][‘designation’]

[Optional] User’s Designation

string

attendee[0][‘company’]

[Optional] User’s Company

string

attendee[0][‘city’]

[Optional] User’s City

string

attendee[0][‘country’]

[Optional] User’s Country

string

attendee[0][phone]

[Optional] User’s Mobile with Country Code

int

attendee[0][‘noEmail’]

[Optional] 1 means No notification to the user. By default notification will be sent to the user.

string

attendee[0][‘response'][Custom Question Unique Id][]

[Optional] Custom question Id can be retrieved from oDASH (RSVP Settings > RSVP Form) Refer to GIF image below

array

attendee[0][‘ticketTypeId’]

[Optional] Only applicable in case a ticket is purchased.

Id of ticket which is bought.

int

attendee[0][‘ticketName’]

[Optional] Only applicable in case a ticket is purchased.

Name of ticket which is bought.

string

attendee[0][‘ticketPrice’]

[Optional] Only applicable in case a ticket is purchased.

Price of ticket which is bought.

int

billing[‘orderNo’]

[Optional] Only applicable in case a ticket is purchased.

Unique Id for purchased transaction.

string

billing[‘datePurchased’]

[Optional] Only applicable in case a ticket is purchased.

Unique Id for purchased transaction.

string

billing[‘quantity’]

[Optional] Only applicable in case a ticket is purchased.

Total No of ticket purchased for given order No.

int

billing[‘ticketcost’]

[Optional] Only applicable in case a ticket is purchased.

Total Paid amount of ticket(s) purchased for given order No.

int

billing[‘billingname’]

[Optional] Only applicable in case a ticket is purchased.

Purchaser’s Name for given orderNo.

string

billing[‘billingemailid’]

[Optional] Only applicable in case a ticket is purchased.

Purchaser’s Email for given orderNo.

string

billing[‘buyerPhoneNo’]

[Optional] Only applicable in case a ticket is purchased.

Purchaser’s Mobile for given orderNo.

int

billing[‘currency’]

[Optional] The currency in which the ticket is purchased. Example- INR, USD

string

billing[‘noEmail’]

[Optional] 1 means No notification to the user. By default notification will be sent to the user.

string

NOTE: TO ADD CUSTOM QUESTION

RESPONSE

FORMAT

JSON

SCHEMA

Parameter

Description

status

Contains the status code and message

message

Reason for failed

userInfo.floorLink

One Click Link to join event on FLOOR

EXAMPLE

1. Response in case of success

2. Response in case of failed

ERROR

status

Description

1

User Successfully Registered

0

User Registration Request Failed.

SCENARIO

1. Register a user

[PHP] [CURL]

REQUEST:

<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL,’https://api.10times.com/v1/register’); curl_setopt($ch, CURLOPT_POST, 1);

/* POST PAYLOAD START */

$data['key']=<provided-by-10times>;

$data['event'] = <eventId on which registration to be done>

/* Attendee Details */

$data[‘attendee’][‘0’][‘name’]=”Dev”;

$data[‘attendee’][‘0’][‘email’]=”xxx@xxx.com”;

$data[‘attendee’][‘0’][‘designation’]=”Developer”;

$data[‘attendee’][‘0’][‘noEmail’]=”1”;

$data[‘attendee’][‘0’][‘response’][123][]=”Female”;

$data[‘attendee’][‘0’][‘response’][456][]=”manufacturer”;

/* POST PAYLOAD END */

curl_setopt ($ch, CURLOPT_POSTFIELDS, http_build_query($data)); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);

$result = curl_exec($ch);

?>

2. Register users with purchased ticket

[PHP] [CURL]

REQUEST:

<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL,’https://api.10times.com/v1/register’); curl_setopt($ch, CURLOPT_POST, 1);

/* POST PAYLOAD */

$data['key']=<provided-by-10times>;

$data['event'] = <eventId on which registration to be done>

$data[‘channel’] = <channel from which registration to be done>

/* Ticket Buyer Details */

$data[‘billing’][‘orderNo’]=”XXXXX-XXXXX-XXXXX”;

$data[‘billing’][‘datePurchased’]=”2020-09-03 13:00:01”;

$data[‘billing’][‘quantity’]=”2”;

$data[‘billing’][‘ticketcost’]=”118”;

$data[‘billing’][‘billingname’]=”Dev”;

$data[‘billing’][‘billingemailid’]=”xxx@xxx.com”;

$data[‘billing’][‘buyerPhoneNo’]=”+91 - XXXXX XXXX”;

$data[‘billing’][‘currency’]=”INR”;

/* First Attendee Details */

$data[‘attendee’][‘0’][‘name’]=”Dev”;

$data[‘attendee’][‘0’][‘email’]=”xxx@xxx.com”;

$data[‘attendee’][‘0’][‘designation’]=”Developer”;

$data[‘attendee’][‘0’][‘noEMail’]=”1”;

$data[‘attendee’][‘0’][‘ticketTypeId’]=”123”;

$data[‘attendee’][‘0’][‘ticketName’]=”Bussiness”;

$data[‘attendee’][‘0’][‘ticketPrice’]=”50”;

$data[‘attendee’][‘0’][‘response’][123][]=”Male”;

/* Second Attendee Details */

$data[‘attendee’][‘1’][‘name’]=”Sam”;

$data[‘attendee’][‘1’][‘email’]=”xxxx@xxx.com”;

$data[‘attendee’][‘1’][‘designation’]=”PM”;

$data[‘attendee’][‘1’][‘noEMail’]=”1”;

$data[‘attendee’][‘1’][‘ticketTypeId’]=”123”;

$data[‘attendee’][‘1’][‘ticketName’]=”Bussiness”;

$data[‘attendee’][‘1’][‘ticketPrice’]=”50”;

$data[‘attendee’][‘1’][‘response’][123][]=”Female”;

/* POST PAYLOAD */

curl_setopt ($ch, CURLOPT_POSTFIELDS, http_build_query($data)); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);

$result = curl_exec($ch);

?>

WHITELIST IP

Requests from whitelist IP will be allowed.

Did this answer your question?