Blog

Brad Wood

March 27, 2014

Spread the word


Share your thoughts

REST APIs are a popular and easy way to add HTTP endpoints to your web applications to act as web services for third parties or even other internal systems. REST is simpler and requires less verbosity and overhead than other protocols such as SOAP or XML-RPC. Creating a fully-featured REST API is easy with the ColdBox Platform. Everything you need for creating routes, massaging data, and enforcing security comes out of the box.

The ColdBox MVC Platform has had excellent support for REST APIs for years and is a great choice for your next project.  Using ColdBox automatically affords you many productive features, including (but not limited to) the following:

  • Flexible and simple URL Routing
  • No XML configuration!
  • Easy use of conventions
  • Built-in data rendering
  • Easy control of HTTP verbs and status codes
  • Error Handling
  • Security
  • Caching

Have a read through our ColdBox REST documentation: Building ColdFusion Rest APIs

Also check out our companion project that helps you write and test REST APIs called ColdBox Relax: ReSTful Tools For Lazy Experts

 

Add Your Comment

(2)

Mar 28, 2014 16:44:10 UTC

by Henry Ho (@henrylearn2rock)

Question, can you how does ColdBox REST support compare to CF10's RESTFul API support?

Would CB's be easier to test / reload vs CF10's implementation?

Mar 28, 2014 16:55:55 UTC

by Luis Majano

Henry, cf10's approach to rest is very rigid in my opinion. Ours is based on MVC best practices and the other one on just creating CFCs with all kind of annotations to expose the end points. YOu have to reload configurations with cf10 and there is not one place where you can see your routing or even alias routing.

With ColdBox, we create a router file approach where you can define your URL mappings and use it not only for REST but for much more. It also allows for MVC to shine with your RESTFul application.

Me personally, I would never leverage the built-in RESTful services as it is too messy in my opinion.

Recent Entries

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Spring Boot developers know the pain of evaluating view technologies. Thymeleaf is great — until you need more expressiveness. FreeMarker is powerful — until the syntax fights you. What if you could write templates in a dynamic JVM language that gives you the full power of the platform, feels natural, and requires zero setup to integrate?

Meet the BoxLang Spring Boot Starter.

Luis Majano
Luis Majano
March 13, 2026
Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

The growing need to evolve legacy financial platforms safely

Many Swiss banks and financial institutions still operate important systems built on ColdFusion and CFML platforms.

These systems manage a wide range of functions, including:

  • internal banking workflows
  • reporting systems
  • client portals
  • data integration platforms
  • compliance and risk management tools

In many cases, thes...

Cristobal Escobar
Cristobal Escobar
March 13, 2026
Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Many ColdFusion environments operate in a reactive mode without realizing it.

Everything seems fine… until something breaks.

A server crashes.

Performance drops suddenly.

An integration stops working.

A security audit reveals missing patches.

At that point the response is urgent:

“Can someone help us fix this now?”

Emergency support is sometimes unavoidable. But when reactive intervention becomes the norm, it usually means something deep...

Cristobal Escobar
Cristobal Escobar
March 12, 2026