Nexus API — Release Notes — May 3, 2019

Enhancements

Good data is specific data. With that in mind, MX will soon add nine new account subtypes to our Nexus API.

These new subtypes will certainly improve the quality and capabilities of Nexus. The following subtypes are included in this enhancement:

However, because these new subtypes are enums, they have the potential to cause integration problems without appropriate preparation.

Thus, we are providing early access to this enhancement so partners can test and adjust integrations to avoid any potential problems. Partners will be able to access these new subtypes for one month prior to the general release. They can do so by using a specific pre-release Accept header in requests to Nexus. Details on how to do this are below.

MX will be adding more new enum values to some resources in the near future. We strongly encourage partners to design their Nexus integrations such that new enum values can either be safely accommodated or ignored without breaking an integration.

Early access to this enhancement is available now. This enhancement will be released for all partners on June 3, 2019.

Using the MX pre-release Accept header

Use the following value for the HTTP Accept header on all Nexus requests to access pre-release features; in this case, nine new account subtype enums. Note the .pre. that has been added.

application/vnd.mx.nexus.v1.pre+json

When using this header, applicable accounts will have one of the new subtypes rather than null.

These new subtype enums will be returned when using the standard header beginning on June 3, 2019.