Slope · AsyncAPI Specification

Slope Webhook Events

Version v4

Generated event surface for Slope webhooks. Payload schemas documented at https://developers.slopepay.com/docs/schema. Signed via the Slope-Signature header (HMAC-SHA256).

View Spec View on GitHub CompanyFintechPaymentsEmbedded FinanceBNPLLendingCreditB2BCheckoutAsyncAPIEvents

Channels

so.slope.customer.created
subscribe
New customer is created
so.slope.customer.updated
subscribe
Customer object updated by you or Slope (e.g. limit or overdue order count change)
so.slope.customer.authorized
subscribe
Customer authenticated into the Slope widget and authorized access to the merchant
so.slope.customer.authorization_revoked
subscribe
Customer closed their account and unauthorized access to the merchant
so.slope.customer.application_submitted
subscribe
Customer submitted an application to Slope
so.slope.customer.credit_decision_reached
subscribe
Customer approved or rejected for a limit
so.slope.prescreen.ready
subscribe
Prescreen succeeded and the result is ready
so.slope.order.opened
subscribe
An order reached the open state
so.slope.order.finalizing
subscribe
An order triggered finalize and is in the finalizing state
so.slope.order.finalized
subscribe
An order reached the finalized state
so.slope.order.adjustment.created
subscribe
An order adjustment (refund) has been created
so.slope.transactions.updated
subscribe
A repayment happened on an order

AsyncAPI Specification

Raw ↑
asyncapi: 2.6.0
info:
  title: Slope Webhook Events
  version: v4
  description: Generated event surface for Slope webhooks. Payload schemas documented at https://developers.slopepay.com/docs/schema.
    Signed via the Slope-Signature header (HMAC-SHA256).
x-apievangelist:
  generated: '2026-07-21'
  method: generated
  source: https://developers.slopepay.com/docs/event-types
defaultContentType: application/json
channels:
  so.slope.customer.created:
    subscribe:
      summary: New customer is created
      message:
        name: so_slope_customer_created
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.customer.updated:
    subscribe:
      summary: Customer object updated by you or Slope (e.g. limit or overdue order count change)
      message:
        name: so_slope_customer_updated
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.customer.authorized:
    subscribe:
      summary: Customer authenticated into the Slope widget and authorized access to the merchant
      message:
        name: so_slope_customer_authorized
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.customer.authorization_revoked:
    subscribe:
      summary: Customer closed their account and unauthorized access to the merchant
      message:
        name: so_slope_customer_authorization_revoked
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.customer.application_submitted:
    subscribe:
      summary: Customer submitted an application to Slope
      message:
        name: so_slope_customer_application_submitted
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.customer.credit_decision_reached:
    subscribe:
      summary: Customer approved or rejected for a limit
      message:
        name: so_slope_customer_credit_decision_reached
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.prescreen.ready:
    subscribe:
      summary: Prescreen succeeded and the result is ready
      message:
        name: so_slope_prescreen_ready
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.order.opened:
    subscribe:
      summary: An order reached the open state
      message:
        name: so_slope_order_opened
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.order.finalizing:
    subscribe:
      summary: An order triggered finalize and is in the finalizing state
      message:
        name: so_slope_order_finalizing
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.order.finalized:
    subscribe:
      summary: An order reached the finalized state
      message:
        name: so_slope_order_finalized
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.order.adjustment.created:
    subscribe:
      summary: An order adjustment (refund) has been created
      message:
        name: so_slope_order_adjustment_created
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema
  so.slope.transactions.updated:
    subscribe:
      summary: A repayment happened on an order
      message:
        name: so_slope_transactions_updated
        contentType: application/json
        x-schema-docs: https://developers.slopepay.com/docs/schema

Work with this as data

Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for asyncapi

4 MCP tools reach this
  • find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/slope-events-asyncapi"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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