Some times, you just need to store some additional metadata on your core entities, like a “CRM ID” on a customer, an “external order ID” on a license, or special entitlements that a trial may have. Until now, you would have to store this in your own database, to be able to enrich your products with the properties you need.

Today, this is made easier using Custom Properties right in Moonbase! These properties can be stored on all the main resources in your Moonbase account:

• Products, Product Releases & Bundles

• Licenses & Trials

• Vouchers & Coupons

• Customers

They support typed values, which means you can build up meaningful content on each entity, and consume them easily through our APIs. To make it easy to update these on the fly, there’s a new section in the Moonbase app to update the properties of these entities easily:

These properties can be used for anything you’d need to store and read, either through our core APIs, on your storefront using our public APIs, or even verified inside license tokens! There is a limit on how much content you can store in this: 48Kb worth of data, but that should be plenty for most use-cases.

Core API

Our core API has been updated with endpoints to update these properties across all entities, as well as include them in responses from existing endpoints. This means you can build rich integrations with other systems, and embed more data without needing your own database.

Our documentation has been updated, and you’ll find docs on custom properties.

License Tokens

In certain cases, you may want these properties to be available in your applications in a verifiable manner. That’s why for properties on customers, products, licenses and trials, you can toggle their inclusion in license tokens. This means they will be part of the signed claims as part of issued tokens:

What this also means is that you get these properties through our SDKs automatically as applications re-validate their tokens over time.