CWR Developer Toolset is a set of browsable REST API endpoints, other online tools, instructions, and limited e-mail support, available as a yearly subscription. It’s purpose is to streamline in-house development of a CWR-capable software, either as a stand-alone solution or integrated with our REST API services.

Built upon years of experience and millions of registrations, but also upon salvaging several misguided projects, this toolset is a completely new and unique approach to CWR.

Although some parts of the toolset are aimed at other interested parties as well, the prime users of the toolset are software architects/developers with experience with REST APIs.


The single biggest issue in all CWR-related projects we were called in to salvage, was poor planning. Or, rather, no planning at all. No wonder that “the plan” has not worked out. Projects were delayed for many months, there was a lot of rejected data and receiving parties were rejecting registrations.

Many things have to happen in order to have a working CWR solution, and a good and clear plan is an absolute requirement.

In this toolset, we are describing several workflows, largely based on previous experiences in developing CWR-capable software solutions. Among them, at least one should be close to client’s actual needs. Of course, clients should modify and/or combine them in order to achieve their goals.

The workflows are described in great detail, step-by-step, covering both music publishing and programming aspects. They differ on client’s needs, goals, complexity of requirements, number and experience of developers, and few other factors.

Most workflows are based on using our tools in production, at least temporarily. The rationale here is that having a CWR-capable stand-alone software, compatible with several societies, requires a lot of testing with receiving parties. Once the testing is finished, there is still a lot of work to be done. By using one of our CWR generators, a client can have a working solution much sooner, as CWR is no longer the bottleneck. Making the solution truly stand-alone may still require significant amount of time, but big part of it will be done while the temporary solution is running in production. There is one workflow in which a stand-alone solution is achieved directly.


It is a standard REST API, in production, data is transferred as JSON both ways by default. When appropriate, data is processed as a stream, and can optionally be delivered as another MIME type. All processing is done in RAM, no data is saved on the server. The goal was speed, but it also removes many security concerns.

All endpoints also can be accessed through a Browsable API, so they can simply be tested in a browser without any specific extensions (e.g. Postman). CWR syntax highlighting is included when appropriate, as depicted in the following screenshot.


Subscription Models and Pricing

We have basically only one model - yearly subscription, paid in advance. Price depends on tools included in the subscription and estimated amount of consulting hours. If the subscription does not include consulting nor any of the “standalone” tools, we may agree to a shorter subscription.

In theory, server load has a limit, after which we charge extra, but even large publisher should be well under the limit. The only real limitation is that access to our services can not be shared with third parties, unless this is defined in the contract.

Please understand that this service has no alternative, no competitors, and a very limited market. On the other hand, potential clients range from small publishers all the way to major service providers. Naturally, our prices might be way to expensive for some and peanuts for others. They are based on the formula that the tools would halve the development time and cost about 25% of the developer’s salary for the saved period, also ignoring all other benefits.

When you are contacting us, please do describe in detail who you are and what you need. While we do not have different prices for different client groups, we might have a more affordable solution for you. For example, one can use tools and documentation in our EBR Plus Workflow, but one can also use our EBR to CWR conversion service at 20%, or even 10% of the price. No, it does not do the same thing, but it may get you close for a fraction of the cost.

If you just ask for the price for the tools, this is exactly what you will get. Yearly subscription on the whole toolset, all 20+ tools (5 CWR creators, 5 CWR/AKC parsers, 10 validators and a syntax highlighter), full documentation and basic email support for developers.

Demo and Tool Preview

15-day demo of the Original Workflow, the simplest workflow in the toolset is available upon request. It includes intro documentation for the toolset, complete documentation for this workflow, and access to the following REST API endpoints:

  • CWR Creator - tool that creates CWR from JSON
  • Field Validator - tool for validation of a single field, used in learning phase
  • Multiple Field Validator - accepts the fields in batches, used in form validation
  • Original ACK Parser - tool that parses acknowledgement files

The data structure used in the Original CWR Generator is depicted below. It is very simple, borderline simplistic, and most potential clients need more. Then again, it still takes few working days for an experienced developer to asses the toolset and choose whether they like the approach and want to take the next step.


There is an open source project Django Music Publisher serving as a proof of concept of the Original Workflow. It fully supports registration management of original musical works by an original publisher.