Changing from OAM to OAM-ESAP will be a hard cut-over without dual submission possibility. We will close the OAM system for submissions on a certain date and then after a few days the new OAM-ESAP will open for submissions.
That goes for manual submissions and service-to-service (API) submissions.
We are on the brink of going into Production for the new API that is tailored towards ESAP.
To help with ensuring preparedness of service-to-service submissions after the cut-over we are establishing the Production edition of OAM-ESAP API a few days ahead of the transition date. This early opening is for ensuring production availability and is not representing an alternative submission channel.
NB: Data submitted on the OAM-ESAP API before the opening date will be discarded.
Credentials for getting a JWT token are the same for old OAM and the new OAM-ESAP.
Credentials for submitting on behalf of your customers will not be present, you will get a temporary company to use as Issuer.