This is a repeat and final notification of a forthcoming change affecting our Omnireach customers, please ensure you are ready. We are making changes to the options available for our outgoing API authentication, and as part of this change, we are consolidating and standardising all authentication.
Both the identification API and the library response API will be using “Bearer” as the authentication scheme rather than “bearer” from approximately 6am on the 31st of March. We would not anticipate that this change will affect modern software, but if your API requires a case sensitive “bearer” as the scheme please either change it to being case insensitive or get in touch so that we can set out a migration path.
For reference, the outgoing APIs that we support are:
- External Customer Information API (Library Response API) – uses “bearer” and will change to “Bearer” for bearer token and OAuth authentication
- Webhook API – already uses “Bearer”
- Customer Identification API – uses “bearer” and will change to “Bearer” for bearer token and OAuth authentication
- Tag Processor action – API Query – already uses “Bearer” Tag Processor action – API Event – already uses “Bearer”
If you have any queries regarding the above or need to discuss a migration plan, please contact your account manager to discuss this at your earliest convenience.