Esri offers the following location services:
Visit ArcGIS location services for more information.
You can view the status of ArcGIS location services on status.arcgis.com.
When creating an application that requires access to ArcGIS location services, choose the authentication method that works best for your application. Esri offers two authentication methods depending on your implemetation.
If you would like to use an API key, you can associate specific referrers and scope the API keys to particular services. See the Security and Authentication section of the Developer Guide for more information.
If you would prefer to use user credentials and authentication through an ArcGIS Platform sign-on, then use OAuth 2.0. This is the recommended method, and is most commonly used with ArcGIS Online and ArcGIS Enterprise. See the Security and Authentication section of the Developer Guide for more information.
See the Pricing page for more details and to estimate costs.
A developer subscription includes the following free tiers for the services listed below:
Please note: if you exceed the free allotment on any of the services above and do not have pay as you go enabled, the service will be disabled until the start of your next monthly term. To ensure uninterupted access, please enable pay as you go on your developer account. For more information on the free tier, go to the pricing page.
Yes, as long as your solution is using location services from the ArcGIS Platform. Please note that you are required to pass an API key or token authentication with all ArcGIS location services that are used by your application, including basemaps and geocoding. See the License and deploy section of the Developer Guide for more information.
If your developer subscription does not have pay as you go enabled or a prepaid balance, the service that has exceeded the free tier will be disabled until the start of your next monthly term.
To restore access to the service, enable pay as you go and you will immediately receive access to the services. To do this, sign in to your dashboard and enable the pay as you go option.
Your account will be invoiced on the same day every month. The invoice day will be based on the day you sign up.
The pay as you go services will be invoiced in US Dollars.
Yes, you can purchase a Monthly Builder Plan by signing in to your dashboard and navigate to the account section. From there, you can purchase a Monthly Builder plan at price of $125 per month with a payment card. If you want to pay with an alternative method, please contact Esri Customer Service or your local distributor.
Yes, when you add a valid payment method when enabling pay as you go, you will receive access to all ArcGIS location services that do not include a free tier. If you have exceeded a free tier and that service has been disabled, access will be restored upon adding a valid payment method when enabling pay as you go.
You can find the terms and conditions on the Esri legal website: https://www.esri.com/en-us/legal/overview.
Yes, the Esri basemap and geocoding API endpoints require authentication. If you are implementing a new application or upgrading an existing application, you will be required to authenticate with these services with either an API key or a token. To get an API key, you can sign in to your developer account and use your dashboard to create an API key. See the License location services section of the Developer Guide for more information.
Go to the documentation to learn more.
Yes, you can create an API key and scope it to a particular service. Refer to Available services for a list of services and scopes. If you have a developer account, you can also scope the API key to an item that belongs to your developer account.
You can host your private data in ArcGIS Platform and use it in your solution. This is currently in beta. While you’re unable to commercially release this capability now, you can develop and test against it. Once the private data feature is released, it will have a transaction-based business model.
Private data hosted in ArcGIS Platform should be used to add value to your solution and not to host data as a service for your customers, nor should it be used as a mechanism to sell data.
You can build and deploy as many revenue generating apps as you want with a developer subscription. Please note that you are required to pass an API key or token authentication with all ArcGIS location services that are used by your application, including basemaps and geocoding. See the License and deploy section of the Developer Guide for more information.
You can restrict access to your API key to specific clients by setting the Allowed Referrers to only the origins you grant access to. Review your API key settings by signing in and going to your dashboard. For more information about API keys, see the Security and Authentication chapter of the Developer Guide.
No. API keys grant access to ArcGIS Platform services, while a Runtime license string is required to license your app built with ArcGIS Runtime. For more information, see License and deploy.
You can license your Runtime app at the Lite level, available for free with your ArcGIS Developer Subscription, or contact your Esri account representative for license strings for paid levels (Basic, Standard, Advanced) or extensions from Esri and distributed via deployment packs.
Yes, each ArcGIS Developer Subscription can generate one unique Runtime Lite license string. This string can be shared across all Runtime apps associated with the ArcGIS Developer Subscription from which it was created. Protect your license string – it is unique to your ArcGIS Developer Subscription.
No, there is no limit.
ArcGIS Runtime Local Server is a component that enhances functionality of desktop-focused ArcGIS Runtime SDKs:
It is available as a separate install to supplement functionality of Runtime SDKs supported on Windows and Linux desktops. It's powered by packages created in ArcMap, which can be hosted by Local Server as local map, feature, and geoprocessing services. Desktop-focused ArcGIS Runtime SDKs also provide a client API to access Local Server services.
Local data files are geo-enabled data available in a file residing on your users device regardless of how it got there. ArcGIS Runtime supports a variety of different local file data formats. Depending on the type of data, a certain license level may be required to use that data in your ArcGIS Runtime app.
License strings for paid levels or extensions are purchased from Esri and distributed via deployment packs. Upon purchase of a deployment pack, you are provided with a unique license string for the level or extension purchased. Additional deployment packs for a level or extension you purchased previously will not include another license string. However, additional unique license strings can be provided on request. Protect your license strings – they are unique to your organization.
ArcGIS Runtime apps are licensed per deployment.
License keys are often used by customers who do not have access to Named User accounts in an ArcGIS Online organization or on-premises ArcGIS Enterprise, need to use an application that will remain offline indefinitely, or need to guarantee an application will function if offline longer than 30 days. Customers are required to track the number of ArcGIS Runtime deployments at the Basic, Standard, and Advanced levels. Each installation of your app available to a single user counts as a deployment.
Named Users are viable for customers who have ArcGIS organizational accounts in an ArcGIS Online organization or an on-premises ArcGIS Enterprise and use devices that will be online at least every 30 days (default timeout for Named User license for ArcGIS Runtime). One notable benefit of this model is the ability to license for ArcGIS Runtime travels with the Named User, not the app, so one Named User can license many ArcGIS Runtime apps.
Yes. You may choose to compile your app with a Lite license key to provide access to Lite functionality in your Runtime app, but also offer the ability to log in with a Named User of type Editor, Field Worker, Creator, or GIS Professional, or a level 2 Named User.
The ArcGIS Runtime license level enabled for a named user is dependent on the user type. Viewer and Lite named user types include a Lite license. Editor, Field Worker, and Basic user types include a Runtime Basic level license. Creator, GIS Pro Basic, and Standard user types include a Runtime Standard level license. GIS Pro Standard, GIS Pro Advanced, and Advanced user types include a Runtime Advanced level license. Some user types do not include an ArcGIS Runtime license, such as Storyteller or Insights.
No. Please contact your Esri account representative for more details on transitioning license strings from 10.2.x to 100.x.
If your inactive developer subscription is deleted, all of your content is deleted from the ArcGIS Platform and cannot be restored.
We delete inactive developer subscriptions for security reasons and it’s an industry best practice.
To prevent the deletion of your inactive developer subscription, all you need to do is sign in to any Esri site with your username, reestablishing activity.
Developer subscription administrators will be notified by email at the email address registered to the account if they are impacted.
Esri determines inactive developer subscriptions by looking at sign ins to any Esri site and service transactions over the last 24 months. If you have signed in to an Esri site within the previous 24 months, or consumed service transactions, then your account is considered active.
If you have pay as you go enabled and have either used a service without a free tier or have exceeded the free tier, your invoice will reflect the total cost per service that has incured usage.
All accounts that access ArcGIS products have different levels of access based on the type of account, license assigned, and services available:
Public account is a free account that is available for individuals to create and share content with limits on usage.
Online account is a member of an ArcGIS Online Organization. Members of an ArcGIS Online Organization will have a user type license assigned and will have access to services based on the role assigned to the member. Online accounts use credits and cannot enable pay as you go.
Developer account is a free account that is included with all ArcGIS Developer Subscription plans and includes access to services with a free tier and the ability to sign into the developer website and other Esri sites. Developer accounts must enable pay as you go to access services beyond the free tier and cannot use credits.
Users with an ArcGIS Online account can sign in to the ArcGIS Developer website to create and manage layers, API keys, and content.
Service credits are the currency used across ArcGIS Online Organizations and are consumed for specific transactions and types of storage, such as storing features, performing analytics, and using premium content. The pay as you go payment option is only offered for Developer Subscriptions and not available to ArcGIS Online Organizations.
Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.