URL Structure

The URL that you will be provided for your embedded app landing page will follow a certain pattern. This page breaks down what each section of the URL is doing.

An embedded app landing page URL will have the following structure:

https://studentbeans.com/[LANGUAGE]/[TERRITORY_CODE]/beansid-connect/embedded-app/[SLUG]

Segment	Example	Purpose
[LANGUAGE]	en-gb	This segment of the URL controls the language the landing page will render in.
[TERRITORY_CODE]	uk	This segment of the URL indicates what territory to load a landing page for. If you only have a landing page in a single territory this segment will always remain the same. If you have landing pages across multiple territories then changing this segment will switch between available territories. If you supply a territory for which there is no landing page set up then an error screen will show.
[SLUG]	example-slug	This segment of the URL is a unique identifier specific to your embedded app landing page. This value will be unique to you and you shouldn't need to change it.

You will be provided with the full link(s) when we set up your embedded app landing page(s) so there's no need to construct these links yourself. An example of a full link might be something like:

https://studentbeans.com/en-gb/uk/beansid-connect/embedded-app/example-slug

info

It is likely that the only time you would need to change the URL yourself is if you want to override the language of the embedded app landing page that you are linking to.

More information on overriding the language of your embedded app landing page can be found on the next page.