Giteki API terms of use
Terms for the free FCCID.io Giteki API: attribution, usage limits, source data and fair use.
Version 1 · Effective October 20, 2026 · Applies to /giteki/api/search.json and /giteki/api/verify.json.
Free access and attribution
Personal and commercial use are free, without registration or a key. When you show API data on a page, app screen or document, include a visible, working link to FCCID.io Giteki and identify Japan’s Ministry of Internal Affairs and Communications (MIC) as the underlying source. An example credit is:
Japan radio certification data: FCCID.io Giteki API. Source: Japan MIC.
Private server-to-server use does not require a public display link. Keep source attribution with any data you redistribute. These conditions concern this hosted API; they do not change the rights that apply to the original government data.
Request limits and caching
Each IP address may make 30 requests in a rolling 60 seconds and 500 requests per UTC calendar day, shared across search and verification. GET and HEAD data requests count, including invalid queries and numbers not found. Documentation, the OpenAPI schema and OPTIONS requests do not count. Excess requests receive HTTP 429 and Retry-After.
Cache records in your application where practical and refresh them daily. Do not bypass limits, bulk-harvest the service, resell API access, conceal the source or disrupt other users. Contact us for larger requirements.
Data and verification
Results come from our published MIC-data catalog. English fields are machine translated; the verification response also includes original source fields. A matched number is a catalog lookup, not a determination of present legal status, label authenticity or whether certification covers a particular device. No match means only that the number was not found in that snapshot.
Availability and responsibility
The service is supplied as available, without guarantees of accuracy, completeness, timeliness or uptime. MIC does not endorse or guarantee this service. Check the official MIC records or an appropriate certification body when you need authoritative confirmation. We may restrict abusive traffic or change or discontinue the API; policy changes will be dated here.