Aapipick
🏷️Brand Logo Search

Logo Search API

Search for brand logos by keyword, optionally narrow by category, inspect available assets, and retrieve the file you need in a cleaner request-and-response workflow.

Brand marksWordmarksAsset retrieval
API Authentication Required
Enter your API key to access this service. All API calls require authentication.

Don't have an API key?

Sign in to your account to create and manage your API keys.

Sign InManage API Keys

Request

Enter a required search term, optionally narrow by category, then submit one request.

GET /api/logos
Category
Quick examples
Request shape
The search parameter is required.
GET /api/logos?search=openai&limit=24

Response

Review matches, inspect the selected asset, then copy or download it.

Ready
No response yet

Submit a search request to load matching logos and inspect the response.

API Integration Guide

Learn how to integrate this API into your applications with code examples and detailed documentation.

API Overview
Search logo metadata by required keyword and optional category filter. The response is an array of matching logo records with asset details.
GET
/api/logos?search=vercel&limit=12

Base URL

https://www.apipick.com

Full Endpoint

https://www.apipick.com/api/logos?search=vercel&limit=12
Parameters
Required and optional parameters for this API
search
required
string

Required keyword for case-insensitive title/slug matching.

Example: openai
category
optional
string

Restrict search to a specific category.

Example: AI
limit
optional
number

Maximum results to return. 1-100.

Example: 24
Code Examples
Copy and paste these examples to quickly integrate the API into your application

cURL Request

curl -X GET "https://www.apipick.com/api/logos?search=vercel&limit=12" \
  -H "x-api-key: YOUR_API_KEY"
Replace YOUR_API_KEY with your actual API key
Response Example
Example response from the API

JSON Response

[
  {
    "id": 371,
    "title": "Vercel",
    "categories": [
      "Vercel"
    ],
    "url": "https://vercel.com",
    "assets": [
      {
        "kind": "logo",
        "theme": "light",
        "filename": "vercel.svg",
        "url": "https://www.apipick.com/logo-library/vercel.svg",
        "width": 76,
        "height": 65,
        "aspectRatio": "76:65",
        "suggestedUseCases": [
          "app icons",
          "favicons",
          "avatars",
          "navigation bars",
          "mobile headers"
        ]
      },
      {
        "kind": "logo",
        "theme": "dark",
        "filename": "vercel_dark.svg",
        "url": "https://www.apipick.com/logo-library/vercel_dark.svg",
        "width": 76,
        "height": 65,
        "aspectRatio": "76:65",
        "suggestedUseCases": [
          "app icons",
          "favicons",
          "avatars",
          "navigation bars",
          "mobile headers"
        ]
      }
    ]
  }
]
Integration Tips

✓Best Practices

  • • Always include x-api-key header
  • • Always handle errors gracefully
  • • Validate input data before sending
  • • Use HTTPS for secure communication
  • • Cache responses when appropriate

ℹResponse Headers

  • • Content-Type: application/json
  • • x-api-key: Required for authentication
  • • Status codes: 200 (success), 400 (error), 401 (unauthorized)
  • • No rate limiting applied

Frequently Asked Questions

Q: What does the search endpoint return?

A: It returns a compact array of logo records with the core fields: id, title, categories, url, and assets, plus asset metadata such as aspect ratio and suggested use cases.

Q: Can I list the full logo catalog without a search term?

A: No. GET /api/logos requires a non-empty search parameter. This endpoint is designed for targeted lookup rather than full-library export.

Q: How do I retrieve a logo file?

A: Search with GET /api/logos, then use the url field in each asset to fetch or embed the file directly — no additional API call needed.

Q: Is this only for SVG logos?

A: No. SVG is the primary format today, and PNG, WebP, and additional asset formats are being added. The search response is already structured around generic asset metadata so clients can support more than one file format cleanly.