<aside> ⚠️

This change will go into effect on May 14th. If you’re ready for it earlier, or need more time to prepare, please let us know.

</aside>

As part of our upcoming Layers feature launch, we're making changes to how Assembled's scheduling system works—and this includes important updates to our API.

📣 What’s changing?

We’re introducing Layers, a new way of modeling overlapping events in schedules. This gives agents and managers the flexibility to see a flattened view of the schedule, which more accurately represents what is actually happening at any given time. This flattened view is also the source of truth for all scheduling metrics.

To align with this updated model, we’re making a change to the GET /activities API endpoint. This will impact how identifiers are generated and returned.

🔄 Summary of the API change

• What’s changing?

  The activity/event identifier returned by the endpoint will change from a UUID to a string type. This is necessary because flattened views can result in identifiers that are not globally unique across overlapping events.

• Why?

  In order to support the added power of scheduling with layers, a single event will be able to have multiple segments in the schedule. To support this, we need more flexibility in how identifiers are structured—hence the change from uuid to string.

• When?

  This change will go live on May 14, 2025. Please make the necessary updates before this date.

🛠 Does this affect you?

Only customers whose systems assume that the event identifier is of the UUID type need to take action.

If you:

• Rely on the identifier being a UUID, or
• Enforce schema validations or constraints expecting UUIDs,

...then your integration may break once this change goes live.

🕐 Can’t update right away?

We’ve got you covered.