specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Openprise
providerId: openprise
created: '2026-05-04'
modified: '2026-08-14'
generated: '2026-08-14'
method: searched
source: https://www.openprisetech.com/pricing
# 2026-08-14: this file previously carried INVENTED limits from the 2026-05-04 bulk
# sweep — free/professional/enterprise tiers at 10/100/1000 requests per minute with
# X-RateLimit-* headers Openprise has never documented. None of that was published by
# the provider. Replaced with the only limits Openprise actually publishes (per-day
# API call allowances on the pricing page) and an explicit record that no response
# headers and no 429 contract are documented. See roadmap#35.
tags:
  - Data Automation
  - Data Quality
  - Marketing Operations
  - RevOps
  - Sales Operations
  - Rate Limiting
  - Quotas
  - Throttling
description: >-
  Openprise publishes per-day API call allowances by plan tier on its pricing page and
  advertises "throttling" as a built-in API Factory capability, but documents no rate
  limit response headers, no exhaustion status code, and no retry or backoff contract.
  The numbers below are the published allowances; the signaling block records what is
  NOT published, which is what an agent actually needs at runtime.
limit_count: 5
headers:
  documented: false
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  note: >-
    No rate limit response headers are documented anywhere in the Openprise Help Center,
    on the API Factory product page, or on the pricing page. Live confirmation is not
    possible: API Factory endpoints are generated per tenant and their URLs are only
    revealed inside the application, and the Openprise Cloud host refuses every
    anonymous request with HTTP 403.
responseCodes:
  documented: false
  throttled: null
  quotaExceeded: null
  note: >-
    No status code is published for allowance exhaustion. The one documented
    quota-related failure is a job-run error string, not an HTTP response —
    "ExceededQuota: ApiBatchItems Limit exceeded", raised when a downstream CRM/MAP bulk
    API quota is hit rather than an Openprise one.
limits:
  - tier: professional
    name: API Factory calls per day
    scope: tenant
    metric: api_calls
    limit: 5000
    timeFrame: day
    floor: true
    published_as: '5,000+ API calls per day'
    applies:
      - API Factory (custom APIs)
    source: https://www.openprisetech.com/pricing
  - tier: enterprise
    name: API Factory calls per day
    scope: tenant
    metric: api_calls
    limit: 10000
    timeFrame: day
    floor: true
    published_as: '10,000+ API calls per day'
    applies:
      - API Factory (custom APIs)
    source: https://www.openprisetech.com/pricing
  - tier: professional
    name: AI orchestration calls per day
    scope: tenant
    metric: api_calls
    limit: 5000
    timeFrame: day
    floor: true
    published_as: '5,000+ API calls per day'
    applies:
      - AI orchestration
    source: https://www.openprisetech.com/pricing
  - tier: enterprise
    name: AI orchestration calls per day
    scope: tenant
    metric: api_calls
    limit: 10000
    timeFrame: day
    floor: true
    published_as: '10,000+ API calls per day'
    applies:
      - AI orchestration
    source: https://www.openprisetech.com/pricing
  - tier: all
    name: Records per Bot run
    scope: job
    metric: records
    limit: 250000
    timeFrame: run
    floor: true
    published_as: '250,000+'
    applies:
      - Bots
      - API Bots
    source: https://www.openprisetech.com/pricing
platform_ceilings:
  - name: Duplicate group size
    limit: 10000
    metric: records
    error: 'errorCode:4001 — Maximum allowed records in a duplicate group is 10000'
    source: https://helpcenter.openprisetech.com/hc/en-us/articles/24107427607572-Error-Error-while-running-job-errorCode-4001-errorMessage-Maximum-allowed-records-in-a-duplicate-group-is-10000-10xxx-records-found-in-a-duplicate-group
  - name: Job resource exhaustion
    limit: null
    note: >-
      "This job has exhausted available resources. Additional resources have been secured
      and will be used for the next run and no changes to the job are required" — a
      documented soft capacity ceiling that self-heals on the next run.
    source: https://helpcenter.openprisetech.com/hc/en-us/articles/24107418620052-Error-This-job-has-exhausted-available-resources-Additional-resources-have-been-secured-and-will-be-used-for-the-next-run-and-no-changes-to-the-job-are-required
policies:
  - name: Throttling
    description: >-
      API Factory is marketed as including "built-in security, API key authentication,
      throttling, high availability, and zero downtime". The throttling algorithm,
      window, burst allowance and client-visible signal are not published.
    source: https://www.openprisetech.com/api-factory
  - name: Downstream vendor quotas
    description: >-
      Several Help Center articles cover how many Marketo, Salesforce Bulk API and Google
      Places calls an Openprise job consumes. Those are the CUSTOMER's quotas at the
      third-party vendor, consumed on the customer's behalf — not Openprise limits — but
      they are the practical throughput ceiling for most Openprise workloads.
evidence:
  - url: https://www.openprisetech.com/pricing
    http_status: 200
  - url: https://www.openprisetech.com/api-factory
    http_status: 200
  - url: https://www.openprisecloud.com/
    http_status: 403
    note: application host refuses anonymous requests, so no live header observation is possible
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com