Thread Details
  • State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 355 subscribers
  • Views 1582 views
  • Users 0 members are here
Forum Actions
Related

Third party integration via API

David Bundock

We have engaged with a third party marketing automation platform.  To get the most from this we would like it and Sugar to talk to each other via an API. 

Do we need to purchase a full Sugar licence to enable this communication or can it be done using a dedicated API user, if so can anyone advise how this is accomplished?

Thanks

David

Parents
  • 0

    Normally we would use a separate user for various reasons during integrations:

    • there is no confusion to users what changes records, especially if the user is clearly named
    • normally integration users have different permissions as regular users (normally integrations act as admin)
    • with the current capabilities, password management is clearer, and there is clear separation also for SSO purposes between integration users and application users
      • especially when leveraging SSO, I am pretty sure that today you would need a non-sso user to complete server to server integrations
    • for 2 way syncs polling based, it allows to easily stop loops based on last modified user on the Sugar side

    --

    Enrico Simonetti

    Sugar veteran (from 2007)

    www.naonis.tech


    Feel free to reach out for consulting regarding:

    • API Integration and Automation Services
    • Sugar Architecture
    • Sugar Performance Optimisation
    • Sugar Consulting, Best Practices and Technical Training
    • AWS and Sugar Technical Help
    • CTO-as-a-service
    • Solutions-as-a-service
    • and more!

    All active SugarCRM certifications

    Actively working remotely with customers based in APAC and in the United States

Reply
  • 0

    Normally we would use a separate user for various reasons during integrations:

    • there is no confusion to users what changes records, especially if the user is clearly named
    • normally integration users have different permissions as regular users (normally integrations act as admin)
    • with the current capabilities, password management is clearer, and there is clear separation also for SSO purposes between integration users and application users
      • especially when leveraging SSO, I am pretty sure that today you would need a non-sso user to complete server to server integrations
    • for 2 way syncs polling based, it allows to easily stop loops based on last modified user on the Sugar side

    --

    Enrico Simonetti

    Sugar veteran (from 2007)

    www.naonis.tech


    Feel free to reach out for consulting regarding:

    • API Integration and Automation Services
    • Sugar Architecture
    • Sugar Performance Optimisation
    • Sugar Consulting, Best Practices and Technical Training
    • AWS and Sugar Technical Help
    • CTO-as-a-service
    • Solutions-as-a-service
    • and more!

    All active SugarCRM certifications

    Actively working remotely with customers based in APAC and in the United States

Children
No Data