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

Opply Rapyd API

The Rapyd API from Opply — 12 operation(s) for rapyd.

Opply Rapyd API is one of 47 APIs that Opply publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Rapyd. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 12 operations across 12 paths, and defines 22 schemas. It is described by OpenAPI 3.0.3, at version 0.0.0.

Requests are made against the base URL https://api.opply.com.

12 operations 12 paths 22 schemas 2 GET10 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.0.0
Base URL
https://api.opply.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Opply Rapyd API declares 2 security schemes for authenticating requests. An API key is passed in the cookie as sessionid (cookieAuth). An API key is passed in the header as Authorization (tokenAuth).

  • tokenAuth — Token-based authentication with required prefix "Token"

Paths & Operations 12

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

Rapyd 12
GET
/api/v1/rapyd/check_kyb/
api_v1_rapyd_check_kyb_retrieve → 200
POST
/api/v1/rapyd/check_pay_in_advance_availability/
api_v1_rapyd_check_pay_in_advance_availability_create body → 200
POST
/api/v1/rapyd/get_checkout_id/
api_v1_rapyd_get_checkout_id_create body → 200
POST
/api/v1/rapyd/get_checkout_id_supplier_terms_pay_by_card/
api_v1_rapyd_get_checkout_id_supplier_terms_pay_by_card_create body → 200
POST
/api/v1/rapyd/kyb/step1/
step1 KYB questionnaire (onboarding)
api_v1_rapyd_kyb_step1_create body → 200
POST
/api/v1/rapyd/payout/callback/
api_v1_rapyd_payout_callback_create body → 200404403429
POST
/api/v1/rapyd/payout/get_redirect_id/
api_v1_rapyd_payout_get_redirect_id_create → 200
POST
/api/v1/rapyd/payout/set_company_type/
api_v1_rapyd_payout_set_company_type_create body → 200
GET
/api/v1/rapyd/payout/status/
api_v1_rapyd_payout_status_retrieve → 200
POST
/api/v1/rapyd/save_customer_card/
Should be called after Payment by Card on FE and before updateorderstatusafterpayment
api_v1_rapyd_save_customer_card_create body → 200
POST
/api/v1/rapyd/update_order_status_after_payment/
api_v1_rapyd_update_order_status_after_payment_create body → 200
POST
/api/v1/rapyd/webhooks/secret_path/
webhook body has such structure: { id: 'wh81a54cf977b0b6b3ee57d870e2d6ec4a', type: 'CUSTOMERPAYMENTMETHODCREATED', data: {some data structure depending on webhook type}, triggeroperationid: '0fd3bdc9…
api_v1_rapyd_webhooks_secret_path_create → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are PricesRetrieve (29 properties), OrderPrices (25 properties), BankAccount (8 properties), RapydCheckoutData (6 properties). Each schema is shown below with its type and property counts.

PayoutCallback
object
3 properties 3 required
PayoutCompanyType
object
1 property 1 required
PayoutCompanyTypeCompanyTypeEnum
string
Sole Proprietor - Sole Proprietor Private Limited Company - Private Limited Company
BankAccount
object
8 properties 2 required
OrderPrices
object
25 properties 15 required
RapydSavePayment
object
4 properties 2 required
KYBVerificationStatusResponse
object
3 properties 2 required
PaymentScenarioEnum
string
inadvance - In Advance ondispatch - On Dispatch
PricesRetrieve
object
29 properties 26 required
AllCurrencies
string
BND - BND QAR - QAR BUK - BUK LVR - LVR ZRN - ZRN SRD - SRD STD - STD BGL - BGL BOB - BOB CUC - CUC DEM - DEM SOS - SOS BOL - BOL BRZ - BRZ BWP - BWP MKN - MKN…
KYBVerificationStatusResponseStatusEnum
string
Not started - Not started Started - Started In Review - In Review Completed - Completed
PaymentAvailability
object
1 property 1 required
RapydPostCheckout
object
4 properties 3 required
RapydSupplierTermsCard
object
1 property 1 required
PaymentMethod
string
card - Card banktransfer - Bank Transfer PAY30 - Kriya 30 PAY30EOFM - Kriya Next Month
SupportedCurrencies
string
EUR - EUR GBP - GBP USD - USD CAD - CAD
BankTransfer
object
3 properties 2 required
RapydCheckout
object
2 properties 1 required
KYBStep1Response
object
1 property 1 required
VirtualBankTransfer
object
3 properties 3 required
RapydCheckoutData
object
6 properties 5 required
KYBStep1
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opply-rapyd-api-openapi.yml Raw ↑

Other APIs Opply publishes across the network.

Opply Activity Feed API
Opply Admin panel API
Opply Agents API
Opply Agreements API
Opply api API
Opply App Orders API
Opply Brain API
Opply Brands API
Opply Buyer Documents API
Opply Buyer Financial Documents API
Opply Buyer Onboarding API
Opply Buyer self-onboarding API
Where this information came from

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