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

VSCO Payments API

The Payments API from VSCO — 3 operation(s) for payments.

VSCO Payments API is one of 34 APIs that VSCO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 6 operations across 3 paths, and defines 16 schemas. It is described by OpenAPI 3.0.0, at version v2.0.0.

Requests are made against 2 base URLs: https://tave.io/v2, https://workspace.vsco.co/api/v2.

6 operations 3 paths 16 schemas 1 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v2.0.0
Base URL
https://workspace.vsco.co/api/v2
Authentication
API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

VSCO Payments API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-API-KEY (ApiKeyAuth). It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Payments 6
GET
/payment
Get a list of payments
listResourcePayment 3 params → 200400429
POST
/payment
Create a payment.
createResourcePayment body → 201400429
GET
/payment/{id}
Get a specific payment
getResourcePayment 1 param → 200400429
PUT
/payment/{id}
Update a specific payment
updateResourcePayments 1 param body → 200400429
DELETE
/payment/{id}
Delete a specifc payment
deleteResourcePayments 1 param → 204400429
POST
/payment/{id}/apply
Apply payment to Order
createResourceApplyPaymentToOrder 1 param body → 201400429

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Payment (20 properties), PaymentAllocation (10 properties), ErrorValidation (4 properties), Error (4 properties). Each schema is shown below with its type and property counts.

Link
object
The target URL indicated in the href property is related to the current resource according to the defined semantics of the link property name.
3 properties 1 required
MoneyAmount
integer
NullableDate
string
A date string consisting of year, month and day in the timezone of the event if specified or the studio.
Error
object
An error.
4 properties
PositiveMoneyAmount
integer
NullableId
string
A ULID entity identifier that is nullable.
ResourceType
string
The type of resource represented.
ServerTimestamp
string
A server timestamp (always in UTC)
Links
object
Each property defines a hypertext link relationship as indicated by a link object or array of link objects. The target URL of each hypertext link relationship…
1 property 1 required
IsHidden
boolean
Whether or not the object is hidden.
PaymentAllocation
object
10 properties 1 required
PaymentCollection
Payment
object
20 properties 2 required
Id
string
A lowercase [ULID](https://github.com/ulid/spec) entity identifier
ErrorValidation
object
A validation error.
4 properties
List
object
A collection (or list) of resources.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vsco-payments-api-openapi.yml Raw ↑

Other APIs VSCO publishes across the network.

VSCO Brands API
VSCO Contacts API
VSCO Custom Fields API
VSCO Discount Types API
VSCO Discounts API
VSCO Event Types API
VSCO Events API
VSCO File Types API
VSCO Files API
VSCO Galleries API
VSCO Job Closed Reasons API
VSCO Job Contacts API
Where this information came from

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