Shell Mobility APIs: Transition to OAuth 2.0

Shell Mobility APIs are transitioning from Basic Authentication to OAuth 2.0.

As part of our ongoing efforts to enhance the security, reliability, and scalability of our API platform, we recommend that customers plan their transition to OAuth 2.0 by the end of Q3 2026.

The hard stop for legacy Basic Authentication APIs has now been confirmed for the end of October 2026. After this date, Basic Authentication APIs will no longer be supported.

Why are we making this change?

The move to OAuth 2.0 aligns with modern industry standards and best practices for API security. OAuth 2.0 provides several important benefits, including:

• Enhanced security through token‑based authentication instead of static credentials
• Improved credential management, including easier rotation and reduced risk of credential exposure
• Better alignment with security and data protection requirements
• Greater scalability and flexibility to support future API enhancements

These improvements help ensure that integrations with Shell APIs remain secure, resilient, and future‑ready.

How to get started

To support you during the transition, we have made detailed documentation and tools available:

• Software Development Kits (SDKs)  
• FAQs for OAuth 2.0 migration

These resources are designed to make the migration as straightforward as possible.

To help ensure a smooth transition, we kindly ask you to confirm that you are aware of this change and share your estimated timeline for completing the migration to OAuth 2.0, so we can provide support where needed.

Should you require any assistance or have any questions regarding the transition, please raise a ticket