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

Pexafy Collections API

Saved sets, owned by an API key.

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

Tagged areas include Collection. 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 12 operations across 8 paths, and defines 20 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.

12 operations 8 paths 20 schemas 4 DELETE4 GET4 POST

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 Collections 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 12

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

collections 12

Saved sets, owned by an API key.

GET
/collections
Collections owned by the calling key
listCollections → 200401429
POST
/collections
Create a collection
createCollection body → 201400401422429
GET
/collections/{collection_id}
One collection
getCollection 1 param → 200401403404429
DELETE
/collections/{collection_id}
Delete a collection
deleteCollection 1 param → 204401403404429
POST
/collections/{collection_id}/photos
Add a photo to a collection
addPhotoToCollection 1 param body → 201200401403404422429
DELETE
/collections/{collection_id}/photos/{photo_id}
Remove a photo from a collection
removePhotoFromCollection 2 params → 204401403404429
GET
/api/v1/collections
List collections
list_collections_api_v1_collections_get → 200422
POST
/api/v1/collections
Create a collection
create_collection_api_v1_collections_post body → 201422
GET
/api/v1/collections/{collection_id}
Get a collection
get_collection_api_v1_collections__collection_id__get 1 param → 200422
DELETE
/api/v1/collections/{collection_id}
Delete a collection
delete_collection_api_v1_collections__collection_id__delete 1 param → 200422
POST
/api/v1/collections/{collection_id}/photos
Add a photo to a collection
add_photo_to_collection_api_v1_collections__collection_id__photos_post 1 param body → 201422
DELETE
/api/v1/collections/{collection_id}/photos/{photo_id}
Remove a photo from a collection
remove_photo_from_collection_api_v1_collections__collection_id__photos__photo_id__delete 2 params → 200422

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are Collection (8 properties), Collection_2 (8 properties), CollectionItem (6 properties), CollectionItem_2 (6 properties). Each schema is shown below with its type and property counts.

Meta
object
2 properties
CollectionItemEnvelope
object
3 properties 2 required
ErrorEnvelope
object
Every failure uses this shape, whatever the status code.
2 properties 2 required
CollectionInput
object
What a client may set on a collection. Deliberately not the same component as Collection: sharing one would make every added response field an edit to the requ…
3 properties 1 required
CollectionEnvelope
object
3 properties 2 required
CollectionItem
object
6 properties 2 required
CollectionListEnvelope
object
3 properties 2 required
Collection
object
8 properties 2 required
Meta_2
object
2 properties
CollectionResponse
object
4 properties
ValidationError
object
3 properties 3 required
CollectionItemResponse
object
4 properties
CollectionCreateBody
object
3 properties 1 required
ApiError
object
3 properties 2 required
HTTPValidationError
object
1 property
AddPhotoBody
object
4 properties 1 required
CollectionItem_2
object
6 properties
CollectionListResponse
object
4 properties
DeletedResponse
object
4 properties
Collection_2
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pexafy-collections-api-openapi.yml Raw ↑

Other APIs Pexafy publishes across the network.

Pexafy Facets API
Pexafy Photos API
Pexafy Search API
Pexafy Usage API
Where this information came from

This is an independent, third-party profile of Pexafy Collections 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.