Flickr API Schema

Name: Flickr API Schema API
Brand: Flickr API
Availability: InStock

✓ Official Vendor SpecMediaImage Processingoauth125 EndpointsREST

For Agents

Search Flickr photos, read photo metadata and EXIF, browse groups, galleries, and favorites, and upload images on behalf of an authenticated user.

Quickstart

Get started with Flickr API Schema in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"search Flickr photos by tag"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Flickr API Schema API.

Search the public Flickr photo corpus by tags, text, license, or user with flickr.photos.search

Read photo metadata, sizes, EXIF data, and license details for any accessible photo

Browse photoset, gallery, and group-pool contexts for a given photo

List the photos a person has uploaded or favorited and read their public profile

GET STARTED

Start building with Flickr API Schema API

Explore with Jentic

View OpenAPI Document

Use for: Search Flickr for Creative Commons photos of the Eiffel Tower, Get the EXIF data for a specific Flickr photo, List all photos a Flickr user has uploaded, Find which group pools contain a given photo

Not supported: Does not handle image editing, video hosting, or payment processing - use for Flickr photo search, metadata retrieval, and authenticated photo upload only.

The Flickr API exposes a Swagger-described subset of Flickr's photo-sharing platform, covering photo and photoset metadata, search, EXIF and license data, group pools, galleries, favorites, and user profiles. It also includes the OAuth request and access token endpoints plus the photo upload endpoint, so an integration can authenticate a user, search the public photo corpus, and read context such as comments, sizes, and discussion threads.

Use Cases

Patterns agents use Flickr API Schema API for, with concrete tasks.

★ License-aware image discovery

Editorial teams and AI agents searching for reusable imagery filter Flickr by license through flickr.photos.search and flickr.photos.licenses.getInfo. Combined with flickr.photos.getSizes, this returns a vetted list of Creative Commons photos at the resolution the publication needs, with attribution data already attached.

Search for Creative Commons photos tagged 'mountains', then return the photo IDs, sizes, and license names for the top 10 results

Photo metadata enrichment

Photo-management tools enrich an image record with EXIF camera and lens data, GPS context, and license metadata pulled from Flickr. The flickr.photos.getInfo, flickr.photos.getExif, and flickr.photos.getSizes calls together expose enough detail to populate a digital-asset-management record from a single photo URL.

Given a Flickr photo ID, fetch its EXIF, sizes, and license, and write a JSON record with camera model, focal length, dimensions, and licence name

Community photo curation

Group administrators and curators read pool members, group info, and discussion topics through flickr.groups.getInfo, flickr.groups.pools.getPhotos, and the flickr.groups.discuss endpoints. This drives moderation tooling and lets curators feature member photos in galleries with citation context.

List the most recent 50 photos in a Flickr group pool and the latest 5 discussion topics in that group

AI agent image research

An AI research agent uses Flickr through Jentic to find Creative Commons reference photos for a writing or design task, retrieve their full sizes and licence names, and cite them correctly. Jentic returns the right Flickr operation for each step of the workflow without the agent browsing all 25 endpoints by hand.

Find five Creative Commons photos of red pandas, return the original-size URL and required attribution string for each

Key Endpoints

25 endpoints — the flickr api exposes a swagger-described subset of flickr's photo-sharing platform, covering photo and photoset metadata, search, exif and license data, group pools, galleries, favorites, and user profiles.

METHOD

PATH

DESCRIPTION

GET

/rest?method=flickr.photos.search

Search the public photo corpus

GET

/rest?method=flickr.photos.getInfo

Get full metadata for a photo

GET

/rest?method=flickr.photos.getExif

Read EXIF data for a photo

GET

/rest?method=flickr.photos.getSizes

List the available sizes and download URLs for a photo

GET

/rest?method=flickr.photos.licenses.getInfo

Look up Creative Commons and other license names

GET

/rest?method=flickr.people.getPhotos

List photos uploaded by a specific user

POST

/upload

Upload a new photo on behalf of an authenticated user

GET

/rest?method=flickr.photos.search

Search the public photo corpus

GET

/rest?method=flickr.photos.getInfo

Get full metadata for a photo

GET

/rest?method=flickr.photos.getExif

Read EXIF data for a photo

GET

/rest?method=flickr.photos.getSizes

List the available sizes and download URLs for a photo

GET

/rest?method=flickr.photos.licenses.getInfo

Look up Creative Commons and other license names

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Flickr OAuth 1.0a consumer keys, secrets, and per-user access tokens are stored encrypted in the Jentic vault. Request signing happens at execution time inside MAXsystem, so the agent context only ever sees the response payload.

Intent-based discovery

Agents search Jentic by intent such as 'find Creative Commons photos of mountains' and Jentic returns the matching flickr.photos.search call with its input schema, removing the need to learn Flickr's REST-over-query method conventions.

Time to first call

Direct Flickr integration: 2-3 days for OAuth 1.0a signing, error handling, and pagination. Through Jentic: under 1 hour to search, load the schema, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Instagram API

Instagram is a competing photo-sharing platform with its own publishing and discovery API

Choose Instagram when the agent needs to publish to a creator's primary social audience rather than browse a Creative Commons photo library

Complementary

Cloudinary Upload API

Cloudinary transforms and serves the images that an agent discovers on Flickr

Use Cloudinary when the agent needs to resize, crop, or CDN-deliver a photo it has located on Flickr

Alternative

Shutterstock API

Shutterstock licenses commercial stock photography rather than browsing user-uploaded Creative Commons content

Pick Shutterstock when the agent needs guaranteed commercial-licensed stock imagery rather than community-uploaded photos

FAQs

Specific to using Flickr API Schema API through Jentic.

What authentication does the Flickr API use?

The Flickr API uses OAuth 1.0a request and access tokens at /oauth/request_token and /oauth/access_token. Through Jentic the OAuth secrets are stored in the encrypted vault and request signing happens at execution time, so an agent never holds the raw consumer secret.

Can I filter Flickr photos by license with the API?

Yes. flickr.photos.search accepts a license parameter, and flickr.photos.licenses.getInfo returns the name and URL for each license code so the integration can render correct attribution.

How do I read EXIF data for a Flickr photo?

Call flickr.photos.getExif with the photo ID. The response returns camera model, lens, focal length, ISO, aperture, and other tags exposed by the photographer.

What are the rate limits for the Flickr API?

Flickr publishes a default cap of 3,600 calls per hour per API key, with bursts subject to throttling. Treat 429 and 503 responses as the source of truth and back off accordingly.

How do I search Flickr photos through Jentic?

Search Jentic for 'search Flickr photos', load the schema for flickr.photos.search, and execute the call with your tags or text query. Install with pip install jentic and sign up at https://app.jentic.com/sign-up.

Can I upload a photo to Flickr through this API?

Yes. POST a multipart upload to /upload with an OAuth-signed Authorization header. The user must have authorized your application with write scope first.