Best way to log API calls that create records

Many of our records are created via an API call from an external source.  Is there a way I can log those calls so I can see what was sent in via the API versus what is in the record now.  I just want an irrefutable way to see what they are sending into the system.

I need to see all the data included in the POST.

Parents
  • There is no-code upgrade safe approach could be applied in case of the the variety of API calls is not too significant

    1. Use Roles to restrict creating records of all modules for the user, which is used loggin via API

    2.Configure a custom endpoint by adding new LB Services record and allow APi user to access this module

    3. Draw a flowchart with Logic Builder that will check the JSON retrieved via custom endpoint and, after logging the JSON, to decide yourself in a flowchart wether to create or update any Sugar records or not and, if nessesary, to return  error-refusal to the inquiring system with explanation

    This approach will make all the API access 100% managable by Sugar Admin an also would help to make  the custom business logic implemented in Sugar respected for the API calls

    Let me know if there is a need of example

    You may also read about Sugar Partner's experience with Logic Builder in Clubs blog:

     sugarclub.sugarcrm.com/.../how-analysts-can-do-more-for-customers-and-their-own-company

    Best Regards,
    Dmytro Chupylka

    integroscrm.com
    We make work in Sugar CRM system faster, more convenient and efficient

Reply
  • There is no-code upgrade safe approach could be applied in case of the the variety of API calls is not too significant

    1. Use Roles to restrict creating records of all modules for the user, which is used loggin via API

    2.Configure a custom endpoint by adding new LB Services record and allow APi user to access this module

    3. Draw a flowchart with Logic Builder that will check the JSON retrieved via custom endpoint and, after logging the JSON, to decide yourself in a flowchart wether to create or update any Sugar records or not and, if nessesary, to return  error-refusal to the inquiring system with explanation

    This approach will make all the API access 100% managable by Sugar Admin an also would help to make  the custom business logic implemented in Sugar respected for the API calls

    Let me know if there is a need of example

    You may also read about Sugar Partner's experience with Logic Builder in Clubs blog:

     sugarclub.sugarcrm.com/.../how-analysts-can-do-more-for-customers-and-their-own-company

    Best Regards,
    Dmytro Chupylka

    integroscrm.com
    We make work in Sugar CRM system faster, more convenient and efficient

Children