Deprecated: Optional parameter $post_id declared before required parameter $field is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/includes/api/api-value.php on line 231

Deprecated: Optional parameter $value declared before required parameter $field is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/includes/api/api-value.php on line 338

Deprecated: Optional parameter $post_id declared before required parameter $field is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/includes/api/api-value.php on line 338

Deprecated: Optional parameter $post_id declared before required parameter $field is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/includes/api/api-value.php on line 396

Deprecated: Optional parameter $post_id declared before required parameter $fields is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/includes/api/api-field.php on line 323

Deprecated: Optional parameter $key declared before required parameter $data is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/includes/cache.php on line 399

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/contact-form-7/includes/form-tag.php on line 339

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/contact-form-7/includes/form-tag.php on line 331

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/contact-form-7/includes/form-tag.php on line 325

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/contact-form-7/includes/form-tag.php on line 343

Deprecated: Optional parameter $i declared before required parameter $post_id is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-repeater.php on line 700

Deprecated: Optional parameter $i declared before required parameter $post_id is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-repeater.php on line 766

Deprecated: Optional parameter $name declared before required parameter $field is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-flexible-content.php on line 1044

Deprecated: Optional parameter $i declared before required parameter $post_id is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-flexible-content.php on line 1080

Deprecated: Optional parameter $i declared before required parameter $post_id is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-flexible-content.php on line 1132

Deprecated: Optional parameter $id declared before required parameter $field is implicitly treated as a required parameter in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/pro/fields/class-acf-field-gallery.php on line 283
Set up as an API user – London Theatre Direct WordPress Plugin

Set up as an API user

Overview

To unlock the full benefits of the plugin it is best to sign up as an API User.

Signing up as an API partner is slightly more complicated than signing up as an AWIN partner or a Whitelabel partner.  You will need to first sign up as a developer, then register an application in order to obtain your API keys.

The main benefit of signing up as an API user is that the plugin will run using your API keys, rather than the default API keys shared by all AWIN and Whitelabel partners.  As all API keys have their own quotas, using your own API keys means you can pull across data more frequently, synchronise products faster, and run your own update processes.

We’ve put together a handy video to show you exactly what you need to do to get your own API keys:


Warning: Trying to access array offset on value of type bool in /home/ukdsco/public_html/ltd.wordpress/wp-content/plugins/advanced-custom-fields-pro/includes/api/api-template.php on line 506

Video Tutorial

Step-by-step

  1. Log into your WordPress website
  2. Using the menu on the left, navigate to Theatre Tickets
  3. Under Partner Settings click API User
  4. Below the input boxes, click Get your keys
  5. On the next screen enter all the required details, including your email address - this is where a confirmation email will be sent which you will need to activate your account
  6. When you receive the confirmation email, click the activation link
  7. On the confirmation screen, click the link that says 'Apply for access to the API'
  8. Fill in the required fields, giving the name of your application (this can be anything; your company name, your website, etc.)
  9. Make sure the checkbox next to 'Issue a new key for the London Theatre Direct REST API Package' is checked. Then check the same for the Sandbox API
  10. Accept the terms and conditions at the bottom of the form and click 'Register Application'
  11. Nearly there now! On the 'Application Registered' screen, find your API and API SANDBOX keys. Copy them and paste them into the corresponding fields in the Partner Settings page
  12. Click save and you are done! The plugin is now setup to use your API Keys. Give yourself a pat on the back!

Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0! Use wp_filter_content_tags() instead. in /home/ukdsco/public_html/ltd.wordpress/wp-includes/functions.php on line 5316

Looking for an easier setup?

To unlock the full benefits of the plugin you should sign up as an API User, however if you prefer you can setup the plugin either as a Whitelabel partner, or using an AWIN (formerly Affiliate Window) ID.