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: Amkor Technology
providerId: amkor-technology
generated: '2026-09-02'
method: searched
source: https://amkor.com/b2b-integration-services-solutions/ and a full walk of amkor.com/page-sitemap.xml
created: '2026-05-04'
modified: '2026-09-02'
# 2026-09-02: this file previously carried a bulk-sweep SCAFFOLD asserting X-RateLimit-* headers and
# free/professional/enterprise throttles (10/100/1000 rpm) that Amkor has never published. Amkor ships
# no web API at all, so there are no limits and no runtime signalling headers. Replaced with the
# probed reality below.
tags:
  - Semiconductor Packaging
  - OSAT
  - Rate Limiting
description: >-
  Amkor Technology documents no API rate limits, because it publishes no web API. Its customer
  integration surface is EDI / RosettaNet / SFTP / AS2 / SOAP, provisioned per customer, and no
  throughput ceilings, quotas or response headers are published for it.
limit_count: 0
headers: {}
responseCodes: {}
limits: []
evidence:
  - url: https://amkor.com/b2b-integration-services-solutions/
    status: 200
    note: >-
      Describes delivery protocols, message formats and 24x7 B2B support; states no throughput limit,
      quota, batch ceiling or throttling behaviour.
  - url: https://amkor.com/openapi.json
    status: 404
  - url: https://api.amkor.com/
    status: 403
    note: Imperva/Incapsula edge denies every anonymous request, so no live 429/Retry-After behaviour is observable.
notes:
  - >-
    An honest zero. Any per-customer throughput agreement would live in the commercial integration
    contract, which is not public.
maintainers:
  - FN: API Evangelist
    email: info@apievangelist.com