- Products ProductsLocation Services
Solve complex location problems from geofencing to custom routing
PlatformCloud environments for location-centric solution development, data exchange and visualization
Tracking & PositioningFast and accurate tracking and positioning of people and devices, indoors or outdoors
APIs & SDKsEasy to use, scaleable and flexible tools to get going quickly
Developer EcosystemsAccess Location Services on your favorite developer platform ecosystem
- Documentation DocumentationOverview OverviewServices ServicesApplications ApplicationsDevelopment Enablers Development EnablersContent ContentHERE Studio HERE StudioHERE Workspace HERE WorkspaceHERE Marketplace HERE MarketplacePlatform Foundation and Policy Documents Platform Foundation and Policy Documents
- Pricing
- Resources ResourcesTutorials TutorialsExamples ExamplesBlog & Release Announcements Blog & Release AnnouncementsChangelog ChangelogDeveloper Newsletter Developer NewsletterKnowledge Base Knowledge BaseFeature List Feature ListSupport Plans Support PlansSystem Status System StatusLocation Services Coverage Information Location Services Coverage InformationSample Map Data for Students Sample Map Data for Students
- Help
HERE Workspace and Marketplace Limits and Quotas
Limits
- For information about data storage and throughput limits, see Storage and throughput limits.
- For information about limits related to orgs, users, projects, and apps, see the Identity & Access Management Guide.
- For information about pipeline quotas and limits, see Pipeline Quotas & Limits.
Quotas
Usually, if a quota is exceeded when making requests to an API, the API returns a HTTP 429/503 status code and a message that the account has exceeded the quota. See the HERE Workspace and HERE Marketplace terms for more information.
Note
In the event of a sudden surge in demand, such as a doubling of traffic levels in a very short period of time, HERE services may return HTTP 429/503 status codes for a short period of time (usually up to 10 minutes) and throttle requests from one or more users, even if the user's quotas were not reached. This is done to enable the service to meet the Service Level Agreement (SLA) while the service adapts to new request rates.
- For information about quotas related to the Data API, see Storage and throughput limits.
- For information about quotas related to the Authentication and Authorization API, see the Identity & Access Management Guide.
Data privacy
Data privacy is of fundamental importance to HERE and our customers. We practice data minimization and don’t collect data we don’t need. And we promote pseudonymity for data subjects wherever a service does not require personal information to function. We employ privacy by design in services we develop. We strive to go beyond mere regulatory compliance and make privacy an integral part of our corporate culture. We believe that our approach to privacy is vital to earning and retaining the trust of our customers - and the bedrock of our future success as a data-driven location platform.
For more information on how data privacy is of fundamental importance to HERE and our customers, see the HERE Privacy Charter.
