Creed

Creed webhooks API

The webhooks API from Creed — 1 operation(s) for webhooks.

Documentation GitHub OpenAPI

Operations 1

POST /api/webhooks/revenuecat Revenuecat Webhook #

Work with this as data

Every API 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 apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
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 API

curl "https://apis.io/api/v1/apis/creed-webhooks-api"

All apis

curl "https://apis.io/api/v1/apis?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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: Creed achievements Webhooks API
  description: Creed API - Christian AI Chatbot
  version: 1.0.0
servers:
- url: https://api.usecreed.com
  description: Base URL declared by the provider in apis.yml (roadmap#122).
tags:
- name: webhooks
paths:
  /api/webhooks/revenuecat:
    post:
      tags:
      - webhooks
      summary: Revenuecat Webhook
      description: 'Single entry point for all RevenueCat webhook events.


        RevenueCat sends every event for the app to this one endpoint regardless

        of product. Each domain service owns its own product-id/event-type

        filtering and no-ops on events that aren''t relevant to it, so the event

        is simply handed to every domain that consumes RevenueCat events.


        Processing is awaited rather than backgrounded, and unexpected errors are

        intentionally left to propagate (see each service''s handle_* method) so a

        genuine failure surfaces as a non-2xx response and RevenueCat retries

        delivery. All DB writes here are idempotent, so a retry is always safe --

        this also means a crash mid-processing just results in RC redelivering,

        rather than the event being silently lost.'
      operationId: revenuecat_webhook_api_webhooks_revenuecat_post
      parameters:
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
                title: Response Revenuecat Webhook Api Webhooks Revenuecat Post
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Supabase JWT token