Official Sugar REST API Postman Collection Is Live!

We’re excited to announce that the official Sugar REST API Collection is now live and publicly available on Postman! 
You can explore it here: https://rest.apidocs.sugarcrm.com/

What’s Inside

This collection is designed to help developers explore, test, and integrate with the Sugar Sell, Sugar Serve, and Sugar Enterprise platforms more efficiently than ever before.

Organized for Real-World Use

We’ve structured the collection around practical needs:

  • Authorization – Everything you need to authenticate and manage tokens.

  • Modules CRUD – Core create, read, update, and delete operations that work across modules.

  • Use Cases – Real-world scenarios like Performance, Advanced Filtering, Upserts, SugarBPM, enum/dropdown handling and more.

Whether you're building a new integration, debugging a sync issue, or optimizing performance, the collection helps you hit the ground running.

Why It Matters

  • No need to copy-paste CURL commands or build your own tools from scratch.

  • Leverage multiple programing language examples through Postman languages

  • Faster prototyping and testing with a ready-to-use API playground.

  • Clear examples based on real-world use cases.

  • Organized by relevance—no hunting through massive lists of endpoints.

Help Us Improve

We built this collection for you, and we want your input to make it even better.

  • Missing an endpoint or use case?
  • Have a custom workflow or internal collection to share?
  • Documentation isn't clear enough or missing?

Send us your feedback, use cases, or even your own Postman collections, we’ll review and, if appropriate, add them to the official version (with credit, if you’d like!).

You can:

  • Drop your feedback in the Developer Community

  • Or email me directly at developers@sugarcrm.com

Let’s build the best possible API experience together.

Enjoy and happy coding.

Parents Comment
  • Thanks  
    I am using n8n - I can pull a very basic field restricted list from accounts (for example) using this 
    /rest/v11_16/Accounts/filter?max_num=50&order_by=id%3ADESC&fields=id,name

    But I haven't been able to work out where to build more complex filters spanning multiple related modules.

    Are Filter expressions like you show in examples 

    filter=[{"name":"Nelson Inc"}] going in Header / Body

    what type is it expecting

    would you do a new field for every filter or build them into one huge expression.

    So far I haven't found a place that i can enter even a single name filter and return on that. 



    Any help or pointers you can give to get started would be great - as I imagine I will have to try and recreate the massive / complex reports that the data guys are building in Sugar in this filterapi...

    (I am advanced Sugar user - wrote most of the original reports used in the business - but newish to api's)

Children