Skip to content

Collins

Bilingual Dictionary and Thesaurus Data

Open documentation ↗
API keyHTTPSNo CORSDictionaries

Verified today: 100% uptime

Is Collins free, and does it need an API key?

No public free tier. You apply for a key through Collins' form, saying which dictionaries you need and whether use is commercial or non-commercial, and Collins sets the terms.

Price
By application
API key
By application

How to get a Collins API key

  1. Fill in the Collins API application form.
  2. Pick the dictionaries you need and choose commercial or non-commercial use.
  3. Wait for Collins to reply with a key and its terms.

Checked by hand on 2026-10-24 against Collins API and Collins API: apply for a key. Providers change their terms, so confirm on their own pages before you commit.

API key

By application

HTTPS

Supported

Browser calls

No, needs a proxy

Status

Live · 100/100

Overview & Architectural Role

Collins provides programmatic access to bilingual dictionary and thesaurus data. Delivered over secure HTTPS protocols, it exposes structured endpoints designed to integrate cleanly into modern frontend frameworks, backend microservices, and automated data pipelines without requiring local database provisioning.

Who it is built for

Engineers building web dashboards, mobile applications, CLI utilities, or background cron workers in need of reliable dictionaries data feeds.

Architectural Advantage

Consuming Collins removes the operational overhead of running custom scrapers, orchestrating headless browser fleets, or manually seeding and maintaining a local database. Instead of reverse-engineering volatile DOM layouts or dealing with anti-bot IP blocks, your application connects directly to a standardized JSON interface designed for backend ingestion with consistent schema schemas. Dedicated authentication ensures rate quotas and credential tracking per project environment.

What our checks found

Health score
100/100
Reliability
100%
Average latency
609ms

Last checked 2026-10-24. Measured independently, not self-reported by the provider.

Core Use Cases & Architecture Ideas

Practical real-world patterns for integrating Collins into software systems.

Automated SaaS Feature Integration

Embed data and functionality from Collins directly into application onboarding, profile enrichment, or reporting dashboards.

Architecture: Backend service worker fetches Collins during user workflows, caches responses in Redis, and hydrates UI state.

Scheduled Reporting & Monitoring Bot

Periodically extract updates from Collins to generate daily digests, analytics reports, or Slack notifications.

Architecture: A scheduled GitHub Action or cron worker executes a lightweight script calling Collins, formatting markdown summaries for stakeholders.

Rapid Prototyping & Hackathon Showcase

Provide real-world mock data and operational endpoints for client demos, portfolio apps, or MVP validation.

Architecture: Static client SPA queries Collins directly to populate mock dashboards, graphs, and interactive UI states without a custom backend.

Code Implementation Examples

Production-ready starting templates with error handling for Collins.

// Requires an API key. Check the docs for whether it goes in a header or a query parameter.
// Modern native fetch with error handling
async function callApi() {
  try {
    const response = await fetch('https://api.collinsdictionary.com/api/v1/resource', {
      method: 'GET',
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY',
      Accept: 'application/json',
    },
    });

    if (!response.ok) {
      throw new Error(`HTTP ${response.status}: ${response.statusText}`);
    }

    const data = await response.json();
    console.log('Response payload:', data);
    return data;
  } catch (error) {
    console.error('API request failed:', error);
    throw error;
  }
}

// callApi();

This API does not send CORS headers, so a browser will block a direct call from your front end. Call it from your server, or put a small proxy in front of it.

Response Payload & Live Testing

Inspect the expected JSON structure returned by Collins.

Expected JSON Response Payload

Authentic sample payload structure to evaluate schema attributes before integration.

{
  "status": 200,
  "api": "Collins",
  "endpoint": "/collins",
  "data": {
    "id": 101,
    "title": "Collins Sample Payload",
    "description": "Bilingual Dictionary and Thesaurus Data",
    "verified": true,
    "category": "Dictionaries",
    "updated_at": "2026-10-24T07:39:09.943Z"
  },
  "meta": {
    "response_time_ms": 609,
    "cached": false
  }
}
Format: application/json

Integration Considerations & Best Practices

Technical factors to keep in mind when integrating Collins into production environments.

Implement In-Memory or Edge Caching

Avoid triggering rate limits on public feeds by caching response payloads in Redis, Vercel KV, or standard HTTP Cache-Control headers with a 5-to-15 minute TTL.

Shield Credentials in Backend Route Handlers

Never expose private API keys in client-side JavaScript or bundle environments. Proxy requests through a Next.js API route or serverless backend to keep secret keys out of public DevTools inspection.

CORS Proxy Required for Browser Frontend Calls

This API does not send Access-Control-Allow-Origin response headers. Direct fetch() calls from browser JavaScript will fail due to Same-Origin Policy. Route your calls through a server backend or lightweight edge proxy.

Validate HTTP Status Before Parsing JSON

Always inspect response.ok before executing response.json(). Upstream services returning 4xx or 502 Bad Gateway often serve HTML error pages, which cause syntax errors when parsed as JSON.

Where this listing comes from

Aggregated from one public source (public-apis), then normalised and checked by us.

Report an issue with this listing ↗

Other Dictionaries APIs

See all 16 →

Random Lexicon

Dictionaries

Random words and definitions using optional filters

No keyCORSHTTPS

Verified today: 100% uptime

View Details

Chinese Text Project

Dictionaries

The CTP API provides integration methods for connecting the functionality and content of the Chinese Text Project with external web applications. It consists of a Plugin API for adding external tools and a JSON API for leveraging CTP features externally.

No keyHTTPS

Verified today: 100% uptime

View Details

Synonyms

Dictionaries

Synonyms, thesaurus and antonyms information for any given word

API keyCORSHTTPS

Verified today: 100% uptime

View Details

Free Dictionary

Dictionaries

This API allows users to access word definitions, phonetics, and usage examples by sending a request with a specific English word. It serves as a resource for developers building applications that require linguistic data, enhancing learning and communication tools.

No keyHTTPS

Verified today: 0% uptime

View Details

Collins — common questions

Answered from what our own scheduled checks found, not from the provider's marketing.

Is the Collins API free?

No public free tier. You apply for a key through Collins' form, saying which dictionaries you need and whether use is commercial or non-commercial, and Collins sets the terms. Checked on 2026-10-24.

Does Collins need an API key?

Yes, and you have to apply for it rather than sign up instantly.

How do I get a Collins API key?

1. Fill in the Collins API application form. 2. Pick the dictionaries you need and choose commercial or non-commercial use. 3. Wait for Collins to reply with a key and its terms.

Can I call Collins from browser JavaScript?

Not directly. Collins did not return CORS headers when we checked, so the browser will block your page from reading the response even though the request itself succeeds. Call it from a server, or put a small proxy in front of it.

Is Collins still working?

Yes, as of 2026-10-24. Our automated check reached Collins and recorded a 100% reliability score with a median response time of 609 ms. We re-check on a schedule, and this page updates with the result.