• Skip to main content

BrilliantConnect

Advanced integration code modules for FileMaker

  • Explore
  • Pricing
  • My Account
    • Log In
    • Purchase History
    • Manage Subscriptions
    • License Keys
    • Preferences
    • Support
  • Docs
    • System Requirements
    • Installation
    • Setup
    • Usage
    • Knowledge Base
  • About
    • Contact
    • Terms & Conditions
    • Privacy Policy

Functions

BrilliantConnect: Verify License

Provide an fmFlare License Key and register your server with LuminFire. Returns the current license status and other information. Your server domain name will be passed, and if it is not registered with LuminFire, will take an available slot.

SharpSpring: Get Leads Date Range

Retrieves a list of Leads that have been either created or updated between two timestamps. Timestamps must be specified in Y-m-d H:i:s format. If FIELDS is specified, only the fields requested will be returned.

SharpSpring: Get Leads

Retrieves a list of Leads given a WHERE clause, or retrieves all Leads if WHERE clause is empty. If a list is used in the parameters, then non-list parameters will be ignored. A maximum of 500 leads will be returned with list ID being selected first. If FIELDS is specified, only the fields requested will be returned.

SharpSpring: Create or Update Leads

Specifies a list of Lead objects to be created in SharpSpring. Every lead object is a hash-keyed by the system name of the lead field. If you wish to push custom fields, first use the getFields API method in order to retrieve a list of custom fields. In order to set a custom field for a lead, use the field’s systemName attribute as the key.

This method accepts up to 500 lead objects per call. However, in instances with a great deal of of custom field data being passed, it is better to separate the requests into smaller, more manageable calls to improve performance. 250 lead objects should be used in those cases.

Specifies a list of Lead objects to be updated in SharpSpring. Every lead object is a hash-keyed by the system name of the lead field. If you wish to push custom fields, first use the getFields API method in order to retrieve a list of custom fields. In order to set a custom field for a lead, use the field’s systemName attribute as the key. This differs from updateLeads in that it returns error code 404 if the lead ID does not exist or the lead ID is not provided and the lead email does not exist.

WordPress: Custom API Request

This is the advanced mode for developers who are comfortable working with the WordPress API. You provide the HTTP method, URL, auth credentials, and URL params and/or body, and it sends it for you. Basically, a thin wrapper around the cURL command.

  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 25
  • Page 26
  • Page 27
  • Page 28
  • Page 29
  • Interim pages omitted …
  • Page 74
  • Go to Next Page »
  • Pricing
  • Support
  • Account
  • Terms
  • Privacy Policy
  • Contact

Copyright © 2025 LuminFire · Log in