How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Pexafy

Pexafy Photos API

One photo at a time.

Documentation Provider Profile APIs.io OpenAPI GitHub

Pexafy Photos API is one of 5 APIs that Pexafy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Photos. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and pricing.

This API exposes 4 operations across 4 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.pexafy.com/api/v1, https://api.pexafy.com.

4 operations 4 paths 23 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.pexafy.com
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Pexafy Photos API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (apiKey). An API key is passed in the header as x-api-key (ApiKeyAuth).

  • apiKey — Send the key as a bearer token. Keys carry scopes; a read scoped key gets a 403 on anything under /collections.
  • ApiKeyAuth — Pass your Pexafy API key in this header. Get your API key at [pexafy.com/dashboard/api-keys/create](https://pexafy.com/dashboard/api-keys/create/).

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

photos 4

One photo at a time.

GET
/photos/{photo_id}
Fetch one photo
getPhoto 1 param → 200401404429
GET
/photos/{photo_id}/similar
Photos that look like this one
getSimilarPhotos 15 params → 200401404422429
GET
/api/v1/photos/{photo_id}
Get a photo
get_photo_api_v1_photos__photo_id__get 2 params → 200422
GET
/api/v1/photos/{photo_id}/similar
Find similar photos
photo_similar_api_v1_photos__photo_id__similar_get 4 params → 200422

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are Photo (21 properties), Photo_2 (21 properties), PhotoUrls_2 (5 properties), PhotoUrls (5 properties). Each schema is shown below with its type and property counts.

Meta
object
2 properties
SearchEnvelope
object
4 properties 3 required
PhotoUrls
object
The same image at five widths. Pick the smallest one that fits; the CDN charges you nothing for it but the upstream library counts a view either way.
5 properties 5 required
Attribution
object
Credit line, ready to drop into a page. Most upstream licences require it even when they do not require a link.
2 properties
ColorName
string
Extensible.
SortBy
string
Extensible.
ErrorEnvelope
object
Every failure uses this shape, whatever the status code.
2 properties 2 required
Pagination
object
Cursor paging. There is no total count: the result set is a ranked stream and counting it would cost more than returning it.
3 properties 2 required
LicenseType
string
Extensible.
PhotoEnvelope
object
3 properties 2 required
Orientation
string
Extensible: new orientations may be added.
Photo
object
21 properties 4 required
Source
string
Upstream library. Extensible: this list grows as libraries are indexed, so parse it as an open string.
Meta_2
object
2 properties
PhotoUrls_2
object
Ready-to-use image links in five sizes.
5 properties
Attribution_2
object
Ready-to-display credit for the photographer/source.
2 properties
PhotoListResponse
object
5 properties
Pagination_2
object
3 properties
PhotoResponse
object
4 properties
Photo_2
object
A photo result. Fields returned can be narrowed with the fields parameter and may depend on your plan.
21 properties
ApiError
object
3 properties 2 required
HTTPValidationError
object
1 property
ValidationError
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pexafy-photos-api-openapi.yml Raw ↑

Other APIs Pexafy publishes across the network.

Pexafy Collections API
AE Profile APIs.io
Pexafy Facets API
AE Profile APIs.io
Pexafy Search API
AE Profile APIs.io
Pexafy Usage API
AE Profile APIs.io
#Photos
← Back to P APIs
API Details
ID
pexafy:pexafy-photos-api
Base URL
https://api.pexafy.com
Docs
https://docs.pexafy.com
Provider
Pexafy
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=pexafy-photos-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/pexafy-photos-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Pexafy Photos API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.