Skip to main content
Membership API

Details of the membership API and how to use it

Cam Langsford avatar
Written by Cam Langsford
Updated over 2 years ago

The Training Tilt API is available to users of our larger plans. View your billing page or our pricing page for more details.

Membership API's

The following api endpoints can be used for automating the membership signup process from external systems such as Infusionsoft but will work with a multitude of other platforms that can execute and HTTP post with parameters.

Scroll to the bottom of the page for an example of an InfusionSoft HTTP post

Subscribe Member

Subscribes a member to a Training Tilt subscription

Attributes 

Path: /api/membersubscriptions/subscribeSupport FormatsJSON, XMLHTTP Method: POST
Secure: Yes
HTTP Codes

  • 200 - Ok

  • 400 - Bad Request. 

  • 500 - Internal Server Error. 

Request

The following table contains the details of a typical HTTP Request for this service:

Method: POST
Path: /api/membersubscriptions/subscribe HTTP/1.1

Content-Type: application/json

Body

{
"applicationKey": "your_api_application_key_goes_here",
"emailAddress":"member@example.com",
"memberReference":"b5cb8a99-ec30-4edb-8dff-12b91c10f6b1",
"tag": "full_membership"
}

Required Fields

applicationKey
email address
tag

Response

Successful Response

This service return no body upon success.

UnSubscribe Member

Un Subscribes a member from a Training Tilt subscription

Attributes 

Path: /api/membersubscriptions/unsubscribeSupport
Formats: JSON, XML
HTTP Method: POST
Secure: Yes
HTTP Codes

  • 200 - Ok

  • 400 - Bad Request. 

  • 500 - Internal Server Error. 

Request

The following table contains the details of a typical HTTP Request for this service:

Method: POST
Path: /api/membersubscriptions/unsubscribe 

Body

{
"applicationKey": "your_api_application_key_goes_here",
"emailAddress":"member@example.com",
"memberReference":"b5cb8a99-ec30-4edb-8dff-12b91c10f6b1",
"tag": "full_membership"
}

Required Fields

applicationKey
email address
tag

Response

Successful Response

This service return no body upon success.

Add Member to a Group

Adds an existing Training Tilt member to a Training Tilt group. The existing Member must have been added using the Subscription Tokens API

Attributes 

Path: /api/addmembergroupSupport FormatsJSON, XMLHTTP Method: POST
Secure: Yes
HTTP Codes

  • 200 - Ok

  • 400 - Bad Request. 

  • 500 - Internal Server Error. 

Request

The following table contains the details of a typical HTTP Request for this service:

Method: POST
Path: /api/addmembergroup HTTP/1.1

Content-Type: application/json

Body

{
"username": "your_api_username_goes_here",
"applicationKey": "your_api_application_key_goes_here",
"memberUsername":"5cb1a31a-5e5b-4cjijijib9-aa90-b4c184f6df16",
"memberReference":"b5cb8a99-ec30-4edb-8dff-12b91c10f6b1",
"groupId": "bf0e4203-ee18-4b3f-a3b7-998a3be9c877"
}

Required Fields

username
applicationKey
memberUsername or memberReference (both or at least one)
groupId

Response

Successful Response

This service return no body upon success.

Remove Member from a Group

Removes an existing Training Tilt member to a Training Tilt group. The existing Member must have been added using the Subscription Tokens API

Attributes 

Path: /api/addmembergroup
Support Formats: JSON, XMLHTTP
Method: POST
Secure: Yes
HTTP Codes

  • 200 - Ok

  • 400 - Bad Request. 

  • 500 - Internal Server Error. 

Request

The following table contains the details of a typical HTTP Request for this service:

Method: POST
Path: /api/removemembergroup HTTP/1.1
Host: https://api.trainingtilt.com/
Content-Type: application/json

Body

{
"username": "your_api_username_goes_here",
"applicationKey": "your_api_application_key_goes_here",
"memberUsername":"5cb1a31a-5e5b-4cjijijib9-aa90-b4c184f6df16",
"memberReference":"b5cb8a99-ec30-4edb-8dff-12b91c10f6b1",
"groupId": "bf0e4203-ee18-4b3f-a3b7-998a3be9c877"
}

 

Required Fields

username
applicationKey
memberUsername or memberReference (both or at least one)
groupId

Response

Successful Response

This service return no body upon success.

Infusionsoft Example

This is the equivalent infusionsoft setup to call one of our POST api endpoints.

Standard HTTP post body

{

      "username": "your_api_username_goes_here",

      "applicationKey": "your_api_application_key_goes_here",

      "memberUsername":"5cb1a31a-5e5b-4cjijijib9-aa90-b4c184f6df16",

      "memberReference":"b5cb8a99-ec30-4edb-8dff-12b91c10f6b1",

     "groupId": "bf0e4203-ee18-4b3f-a3b7-998a3be9c877"

}

Equivalent Infusionsoft HTTP Post set up

Did this answer your question?