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

Spreedly Receivers API

The receivers API from Spreedly — 6 operation(s) for receivers.

Spreedly Receivers API is one of 26 APIs that Spreedly publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 8 operations across 6 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://core.spreedly.com/v1.

8 operations 6 paths 13 schemas 3 GET3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://core.spreedly.com/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Spreedly Receivers API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basic_auth).

  • basic_auth — Unless otherwise noted, all calls to the Spreedly API use [HTTP basic authentication](https://en.wikipedia.org/wiki/Basicaccessauthentication) over HTTPS. Use…

Paths & Operations 8

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

receivers 8
GET
/receivers_options
List supported receivers
list-supported-receivers → 200
POST
/receivers
Create a receiver
create-receiver body → 201403422
GET
/receivers
List created receivers
list-created-receivers 2 params → 200401
GET
/receivers/{receiver_token}
Show a receiver
show-receiver 1 param → 200404
PUT
/receivers/{receiver_token}
Update a receiver
update-receiver 1 param body → 200404422
PUT
/receivers/{receiver_token}/redact
Redact a receiver
redact-receiver 1 param → 200401404
POST
/receivers/{receiver_token}/deliver
Deliver payment method
deliver-payment-method 1 param body → 200401404422
POST
/receivers/{receiver_token}/export
Export payment methods
export-payment-methods 1 param body → 202404

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are payment_method (42 properties), receiver_properties (9 properties), list_created_receivers_response (1 property), export_properties (1 property). Each schema is shown below with its type and property counts.

payment_method
object
42 properties
receiver_properties
object
9 properties
list_supported_receivers_response
object
1 property
deliver
object
1 property
sftp_receiver
object
1 property
deliver_response
object
1 property
http_receiver
object
1 property
errors
array
export_properties
object
1 property 3 required
list_created_receivers_response
object
1 property
export_response
object
1 property
receiver_response
object
1 property
receiver_update
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

spreedly-receivers-api-openapi.yml Raw ↑

Other APIs Spreedly publishes across the network.

Spreedly Access Secrets API
Spreedly Authorize API
Spreedly Capture API
Spreedly Card Refresher API
Spreedly Certificates API
Spreedly Claim API
Spreedly Composer API
Spreedly Credit API
Spreedly Environments API
Spreedly Events API
Spreedly Gateways API
Spreedly General Credit API
Where this information came from

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