Common Works Registration - Developer Toolset


This tool is retired

We have decided to retire this tool. There will be no replacement. Commercial tier was retired in August 2020, as we had no paying clients at the time. And absolutely no interest in new clients.

We know that the free tier is being used, so we will keep it running until 31.10.2020.

For more information about the tools being retired, watch the following video.


CWR Developer Toolset is a set of browsable REST API endpoints, other online tools, instructions, and optional support, available as a yearly subscription. Its 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 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 by receiving parties.

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 your actual needs.

The workflows are described in great detail, step-by-step, covering both music publishing and programming aspects. Most 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 a 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.


It is a standard REST API, data is transferred as JSON both ways. When appropriate, data is processed as a stream. All processing is done in RAM, no data is saved on the server. The goal is speed, but it also removes many legal and 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.

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.

Original Workflow

Original Workflow, the simplest workflow in the toolset, is available for free. It includes intro documentation for the toolset, complete documentation for this workflow, and access to the following REST API endpoints:

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

Original Workflow Schema

The data structure used in the Original CWR Generator is depicted here. It is very simple, borderline simplistic, and most potential clients need more. Then again, it still takes a 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.