Multi-Region Deployment FAQ

Samsara operates in multiple cloud regions. If you build a Samsara integration or marketplace app, you may need separate apps and developer portal access in each region where your customers operate.

This FAQ explains how US, EU, and Canada deployments work for technology partners and customers installing marketplace apps.

Quick reference

How to tell which region you're in: Check the URL in your browser when logged into the Samsara dashboard. Your API requests and OAuth flows must target the matching API base URL.

Note: Some Canadian customers may still be on the US cloud (cloud.samsara.com) and use api.samsara.com. New Canadian deployments on CA cloud use cloud.ca.samsara.com and api.ca.samsara.com. Always match your integration to the customer's dashboard region.

For technology partners

Why do I need apps in multiple developer portals?

Each Samsara cloud region has its own developer portal, app catalog, and customer data environment. A marketplace app published in the US developer portal is not automatically available to customers on EU or CA cloud.

To serve customers in multiple regions, you must:

1. Get a developer portal provisioned for each target region
2. Create and publish a separate app listing in each region's developer portal
3. Point your integration at the correct regional API base URL
4. Complete app certification per region (see App Certification Process)

Samsara cannot republish your app on your behalf. You control when and where your app is listed.

Do I need a separate developer portal account for each region?

Yes. Developer portals are region-specific:

• US: https://cloud.samsara.com/o/<dev_org_id>/developerportal
• EU: https://cloud.eu.samsara.com/o/<dev_org_id>/developerportal
• CA: https://cloud.ca.samsara.com/o/<dev_org_id>/developerportal

You may use the same company and users across regions, but each region requires its own developer org and app listing.

If you already have a US developer portal and want to expand to EU or CA, contact your Samsara partner representative or Partner Support to request regional portal provisioning.

How do I request a developer portal in EU or CA?

1. Ensure you are part of the Technology Partner Program
2. Contact your Samsara partner manager or submit a request via Partner Support
3. Specify which region(s) you need: EU, CA, or both
4. Accept developer terms when you receive your regional invite (invites expire after 24 hours — contact Support to resend if needed)

Can I reuse the same OAuth app credentials across regions?

No. Each regional app listing has its own client ID, client secret, and redirect URIs. OAuth tokens issued in one region are valid only for orgs in that region's cloud.

When building your integration:

• Store the correct API base URL per customer region
• Use region-specific OAuth credentials from the matching developer portal app
• Never send EU customer tokens to api.samsara.com (or vice versa)

We recommend OAuth 2.0 for marketplace apps. Legacy API-token apps do not provide the same one-click install experience and are harder to scale across regions.

What is "Geographies Supported" on my app listing?

When you create an app in App Publisher, Geographies Supported indicates where your solution is available. This metadata helps customers discover your app and tells Samsara which regional marketplace(s) should carry your listing.

If you mark Canada or Europe as supported but only have a US listing, customers in those regions will not see your app until you publish in the corresponding regional developer portal.

See Create and Manage Apps for listing fields.

Do I need to recertify my app in every region?

Yes. Each regional app goes through the App Certification Process independently. Initial certification is a full review; follow-on versions in an already-certified region are typically lighter.

Certification confirms your integration uses the correct regional API endpoints, scopes, and customer enablement steps. Any version upgrades without API scope changes are auto-approved.

How should I test in multiple regions?

Each developer portal includes a sandbox org on the Organizations page. See Sandboxes.

For multi-region testing:

• Create test orgs in each region's developer portal
• Generate API tokens or OAuth flows against the matching regional API base URL
• Validate install and data flow end-to-end before submitting for certification

My integration works in the US — what changes for EU or CA?

Your application code should select the API base URL based on the customer's dashboard region (or a configuration you agree with the customer during onboarding).

For customers

Why can't I find an app that my US peer org has installed?

Marketplace catalogs are region-specific. An app your US subsidiary uses may not yet be published on EU or CA cloud, even if the same vendor integrates with Samsara in the US.

Ask your integration partner:

1. Whether they support your Samsara cloud region
2. When they plan to publish on your regional marketplace
3. Whether a temporary API-token integration is available while marketplace listing is in progress

How do I install a partner app in my region?

1. Log into your Samsara dashboard
2. Go to Settings → Apps
3. Search for the app or use the partner's install link (for beta apps)
4. Complete the OAuth consent flow

Apps only appear if the partner has a published listing in your region's marketplace.

I'm on CA cloud and the install fails / auth errors occur

Common causes:

• The partner's app is listed in the US but not yet on CA cloud
• The partner's backend is still calling api.samsara.com instead of api.ca.samsara.com
• During OAuth, the wrong regional app was selected (some partners operate multiple regional listings)

Contact the app vendor first. If the app should be available in Canada, ask them to confirm their CA marketplace listing status.

Frequently asked questions

Can one Samsara org span US, EU, and CA?
No. Each org lives in a single cloud region. Multi-national companies typically operate separate orgs per region.

Is the API the same across regions?
The REST API surface is largely consistent, but base URLs, data residency, and some region-specific endpoints differ (e.g., EU tachograph). Always use the API Reference with the correct base URL.

Does developers.samsara.com documentation apply to all regions?
Yes. API docs and guides on developers.samsara.com apply globally. Use the regional API base URL that matches your customer's cloud.

Will my US API token work for a CA cloud customer?
No. API tokens and OAuth tokens are scoped to the cloud region where they were created.

I'm a partner — can Samsara copy my US listing to CA/EU for me?
No. You must create and publish listings in each regional developer portal. Samsara partner engineering can assist with onboarding — contact Partner Support.

How long does CA or EU marketplace listing take?
Timelines vary by partner readiness (OAuth migration, regional testing, certification queue). After your regional developer portal is provisioned, most partners complete listing in a few weeks if the integration already works in another region.

Where do I get help?

• Partners: Partner Support
• API / integration questions: Developer community
• Customers: Samsara Support

Related guides

• Partner Developer Portal
• Create and Manage Apps
• OAuth 2.0
• Base URL
• Sandboxes
• App Certification Process