When you create an application that requires access to ArcGIS location services, choose an authentication method compatible with your application. Esri offers two authentication methods:
API keys: A permanent access token that grants your public-facing application access to specific, ready-to-use services and, with an ArcGIS Developer account, private content.
Token based authentication with OAuth 2.0: Temporary tokens using application or user credentials through an ArcGIS Platform sign-on that grant your application access to the services and content authorized to that user or application. This is the recommended method, most commonly used with ArcGIS Online and ArcGIS Enterprise.
Refer to the Security and Authentication section of the Developer Guide for more information.
You can view the status of ArcGIS location services on status.arcgis.com.
Geocoding has different associated costs depending on whether or not you store the results. If you discard geocode results immediately after viewing them on the map or using them in your app, they are not considered stored results.
See the Pricing page for more details and to estimate costs.
Your account will be invoiced on the same day every month. Invoice day is based on the date that you originally signed up.
If your ArcGIS Developer subscription does not have pay-as-you-go enabled or a prepaid balance, the service that exceeds 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 to immediately receive access to the services. To do so, sign in to the ArcGIS Developer dashboard and enable pay-as-you-go.
Yes, when you add a valid payment method and enable pay-as-you-go, you will receive access to all ArcGIS location services not included in the free tier. If you have exceeded your free tier limits and a limited free service has been disabled, access will be restored upon adding a valid payment method when enabling pay-as-you-go.
An ArcGIS Developer subscription includes the following free tiers and services:
Note: if you exceed the free allocation on any of the above services 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 ArcGIS Developer account. For more information on the free tier, refer to the pricing page.
Yes, you can purchase a Monthly Builder plan by signing in to your ArcGIS Developer dashboard and navigating to the account section. From there, you can purchase a Monthly Builder plan with a payment card. Refer to the pricing page for price details.
To pay with an alternative method, please contact Esri Customer Service or your local distributor.
Yes, as long as your solution uses location services from ArcGIS Platform.
Please note that you are required to pass an API key or access token authentication with all ArcGIS location services used by your application, including basemaps and geocoding. Refer to Licensing the use of ArcGIS Location Services in the Developer Guide for more information.
Pay-as-you-go services are invoiced in US Dollars.
You can host your private data in ArcGIS Platform and use it in your solution. This feature is currently in beta. While you’re unable to commercially release this capability at this time, you can develop and test against it. Once the private data feature is released, we will provide a transaction-based business model.
Note: 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.
Yes, Esri basemap and geocoding API endpoints require authentication through ArcGIS Platform. If you are implementing a new application or upgrading an existing application, you will be required to authenticate with these services using either an API key or an access token. Refer to the License location services and Security and authentication sections of the Developer Guide for more information.
See also 2022 migration timelines that will impact your license based on the API or SDK version you use.
Yes, Esri requires that whenever you use ArcGIS basemaps, ArcGIS data services, ArcGIS APIs or SDKs, or other Esri technology in your app, you must include Powered by Esri attribution. Refer to Esri Legal Master Agreements for products, services, and data attribution, and the License your app, and Attribution sections in the Developer Guide for details.
Not if you are using resources from Esri. Whenever you use ArcGIS basemaps, ArcGIS data services, ArcGIS APIs or SDKs, or other Esri technology in your app, you must include Powered by Esri attribution.
Refer to Esri Legal Master Agreements for products, services, and data attribution, and the License your app, and Attribution sections in the Developer Guide for details.
Refer to the documentation to learn more.
Before you deploy your ArcGIS Runtime app into production, you must either license it with one of the four ArcGIS Runtime license string levels: Lite, Basic, Standard, or Advanced, or use ArcGIS Identity (formerly named user login.)
Lite This license level can:
Basic In addition to Lite license functions, this license level can:
Standard In addition to Basic license functions, this license level can:
Advanced In addition to Standard license functions, this license level can:
Not by itself; API keys grant access to ArcGIS Platform services. If you are using an API key with an ArcGIS Runtime API, you must also include a license string to license your app for deployment. Refer to License your app for details.
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, and Advanced), license string extensions from Esri, and distributed 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.
Note: Protect your license string—it is unique to your ArcGIS Developer subscription.
Yes, you can compile your app with a Lite license string to provide access to Lite functionality in your Runtime app, and also offer the ability to log in with an ArcGIS Identity (formerly named user login) type
GIS Professional, or a
level 2 Named User.
ArcGIS Runtime 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 you purchased. Additional deployment packs for a level or extension you purchased previously do not include another license string, however, additional unique license strings can be provided upon request—contact your Esri account representative.
Note: Protect your license strings—they are unique to your organization.
The ArcGIS Runtime license level enabled for ArcGIS Identity is dependent upon the user type.
Some types do not include an ArcGIS Runtime license, such as Storyteller and Insights.
License strings are often used by customers who do not have access to an ArcGIS Online or on-premises ArcGIS Enterprise account or who are using an application that will remain offline for greater than 30 days. You are required to track the number of ArcGIS Runtime license string deployments used at each level (Basic, Standard, and Advanced), as each app installation available (including multiple apps used by a single user) counts as a deployment.
ArcGIS Identity (formerly named user login), is typically used to log in users with an ArcGIS Online or an on-premises ArcGIS Enterprise organizational account, and whose devices or applications will be online at least once every 30 days (the default timeout for ArcGIS Runtime using ArcGIS Identity). A notable benefit of this model is that the license is attached to the user, not the application, so that one authorized user can license more than one ArcGIS Runtime application.
ArcGIS Runtime apps are licensed per deployment.
If you use a license string, you are required to track the number of ArcGIS Runtime license string deployments used at each level (Basic, Standard, and Advanced), as each app installation available (including multiple apps used by a single user) counts as a deployment.
If you use ArcGIS Identity, the license is attached to the user, not the application, so that one authorized user can license more than one ArcGIS Runtime application.
Local data files are geo-enabled data available in a file residing on your users' device(s), regardless of how it got there. ArcGIS Runtime supports a variety of different local file data formats. Depending upon the type of data, a specific license level may be required to use that data in your ArcGIS Runtime app.
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 installation to supplement the functionality of those Runtime SDKs supported on Windows and Linux desktops. It is powered by packages created in ArcGIS Pro, 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.
Refer to the .NET extension licenses documentation, applicable across ArcGIS Runtime API, for more information.
No, contact your Esri account representative for more details on transitioning license strings from 10.2.x to 100.x.
All accounts that access ArcGIS products have different access levels based on their type of account, (optional) subscription, license assigned, and services available:
ArcGIS Developer account is a free account included with all ArcGIS Developer subscription plans and includes access to services with a free tier and the ability to sign into the ArcGIS Developer dashboard and other Esri sites. Developer accounts must enable pay-as-you-go to access services beyond the free tier and cannot use credits.
ArcGIS Online account is a member of an ArcGIS Online organization. Members of an ArcGIS Online organization have a user type license assigned to their organization and have access to services established by their assigned role within the organization. Online accounts use credits and cannot enable pay-as-you-go.
Public account is a free account available for individuals to create and share content with limitations on usage. Public accounts cannot be used to develop applications.
Esri determines inactive ArcGIS Developer subscriptions by reviewing your log-in history to any Esri site and all service transactions over the past 24 months. If you have not signed in to an Esri site within the previous 24 months and have not consumed any service transactions, your account is considered inactive from that date.
Developer subscription administrators are notified by email using the email address registered to their account if their subscription has been determined to be inactive based on account activity and transaction history.
To prevent deletion of an inactive ArcGIS Developer subscription, sign in to any Esri site with your ArcGIS Identity, which reestablishes activity and resets the clock for 24 months from the most recent site activity / transaction history.
If your inactive ArcGIS Developer subscription is deleted, all of your content is permanently deleted from the ArcGIS Platform and cannot be restored.
Esri deletes inactive ArcGIS Developer subscriptions for security reasons. This is a standard industry best practice for risk management and protects both Esri's site and your identity.
Service credits are the currency for specific transactions and storage types, such as storing features, performing analytics, and using premium content, across ArcGIS Online organizations.
Pay-as-you-go is only offered for ArcGIS Developer subscriptions, and is how users with ArcGIS Developer accounts pay for transactions and services that exceed their free tier.
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 your total usage of the cost per service that you have incurred.
If you signed up for an ArcGIS Developer subscription prior to January 27th, 2021, you received 50 credits per month to cover the cost of development and testing with our location services. This $5 voucher is equivalent to the 50 credits you previously received and is part of the transition from service credit pricing to the new ArcGIS Platform pricing model. The voucher represents the free tier each account received prior to January 27, 2021 and will be issued monthly until April 30, 2022.
If you have an ArcGIS Developer subscription, you must migrate from non-metered endpoints to ArcGIS Platform endpoints based on the following timeline for whichever API or SDK you use to develop your application.
If you have an ArcGIS Online or ArcGIS Enterprise account and developed a noncommercial use application, the migration time frames below do not apply.
Please note that the most recent versions of the ArcGIS APIs will use the ArcGIS Platform endpoints.
ArcGIS Runtime SDK
REST API or open source APIs
| Esri Leaflet | ArcGIS REST JS | Supported 3rd party open-source mapping libraries | Applications that utilize the REST endpoints directly | Must migrate to ArcGIS Platform service endpoints by April 30th, 2022. |
Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.