If you have decided that you wish to add Mobile Connect support to your production application you will need to register that application in the Developer Portal. Applications can be registered using the My Applications page on your account page. More details can be found here
For production applications we recommend that you create minimum of three applications. Having three applications registered means that you can easily manage your route through from testing to production.
e.g. If I have an application called My Great App then I might register the following applications.
- My App - Development - with a Redirect URI that works in development (e.g.
- My App - Pre-production - with a Redirect URI that works in pre-production(e.g.
- My App - with a Redirect URI that works in production (e.g.
You may also want additional environments (such as a UAT environment) where you want to run your applications and these should also be registered.
Once you have requested access to an operator API the Redirect URI can no longer be changed. This is for security reasons as the Redirect URI is part of the security chain. If you need to change the Redirect URI then you should create a new application and request access for that application. You will then need to use the credentials from that app with the new Redirect URI.
When registering your applications please consider the following:
- Use a sensible application name that relates to your application.
- Enter a description that clearly states what your application does. If the applications is the test version of a production application then say so in the description.
- Use an application URL that points to your applications web site.
Check any country specific rules that may impact requests for API access
This is only used if you are using the Authorization functionality.
Sector identifier URI
sector_identifier_uri must be a URL using the https scheme that references a file (see example below) with a single JSON array of redirect URLs and/or Service Provider notification endpoint URLs. It provides a way for a group of services under common administrative control to have consistent PCR values independent of the individual domain names. It also provides a way for SPs to change service domains without having to reregister all their users.
[ "https://sp.example.com/redirect_uri1", "https://sp.example.com/redirect_uri2", "https://sp.example.com/notification_uri1", "https://sp.example.com/notification_uri2", "https://sp.example.com/jwks_uri1", "https://sp.other_company.com/jwks_uri2" ]
The Sector Identifier URI value is only needed in Mobile Connect DI v2.3 and above and Mobile Connect SI v1.0 and above. It also requires operator implementation, so your operator will let you know if this functionality in implemented and you must provide this value.
When an application is registered then three sets of Discovery credentials are created. Not all of the credentials will be made available immediately, pre-production and production credentials will only be available once the Mobile Connect Marketing Licence Agreement has been accepted.
These credentials are used when testing application implementation via the Developer Portal Sandbox. The Sandbox is a self contained environment that supports the full end-to-end flow of Mobile Connect and so these credentials will not work in any operator environments.
Making a Discovery request with these credentials will return the Operator pre-production endpoints and Mobile Connect credentials. Operators will notify you if they have a pre-production environment for you to use.
Making a Discovery request with these credentials will return the Operator production endpoints and Mobile Connect credentials. These credentials will only work if you have been provisioned by an operator.