Reo.dev API

Reo.dev API as documented publicly: 18 operations. Contract generated from the documentation by API Evangelist (2026-10-29); not the provider's own document.

Operations 18

GET /accounts/developer-funnel-stages.md Developer Funnel Stages #
POST /api/product/aggregateusage POST /api/product/aggregateusage #
POST /api/product/usage POST /api/product/usage #
GET /audiences/developer-audience.md Developer Audience #
GET /developers.md Developers #
GET /developers/how-to-find-inbound-developers-in-reo.dev.md How to Find Inbound Developers in Reo.Dev #
GET /developers/interpreting-intel-on-the-developer-dashboard.md Interpreting Intel on the Developer Dashboard #
GET /getting-started/for-admins/step-3-find-developers-engaging-with-your-product.md Step 3: Find developers engaging with your product #
GET /getting-started/for-users/step-4-identify-developers-engaging-with-your-product.md Step 4: Identify developers engaging with your product #
GET /install-the-tracking-snippet-with-an-npm-package.md Install the tracking snippet with an NPM package #
GET /install-the-tracking-snippet-with-google-tag-manager.md Install the tracking snippet with Google Tag Manager #
GET /integrations/developer-docs.md Developer Docs #
GET /integrations/input-sources/api-based-integration.md Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: #
GET /integrations/input-sources/api-based-integration/custom-product-events-api.md Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters #
GET /integrations/input-sources/developer-insights.md Developer Insights #
GET /integrations/output-integrations/data-export/zapier.md Zapier #
GET /playbooks/for-aes/track-deal-progression-via-developer-intent-in-your-target-accounts.md Track Deal Progression via Developer Intent in your Target Accounts #
GET /why-a-developer-profile-may-not-be-created-on-reo.dev.md Why a Developer Profile May Not Be Created on Reo.Dev #

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/reodev:reodev-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.

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

OpenAPI Specification

reodev-openapi-generated.yml Raw ↑
openapi: 3.1.0
info:
  title: Reo.dev API
  version: '2026-10-29'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-29: 18 operation(s) read from 21 public documentation page(s) (each
    operation names its page in x-source). This is not the provider''s published contract; Reo.dev has published no machine-readable contract
    that the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 2
    documentation: 16
    pages-with-code: 2
    pages-read: 21
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-29'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://docs.reo.dev/integrations/input-sources/api-based-integration/custom-product-events-api/single-events.md
  - https://docs.reo.dev/integrations/input-sources/api-based-integration/custom-product-events-api/aggregated-events.md
  - https://docs.reo.dev/developers.md
  - https://docs.reo.dev/integrations/developer-docs.md
  - https://docs.reo.dev/audiences/developer-audience.md
  - https://docs.reo.dev/accounts/developer-funnel-stages.md
  - https://docs.reo.dev/integrations/input-sources/developer-insights.md
  - https://docs.reo.dev/install-the-tracking-snippet-with-an-npm-package.md
  - https://docs.reo.dev/integrations/input-sources/api-based-integration.md
  - https://docs.reo.dev/integrations/output-integrations/data-export/api.md
  - https://docs.reo.dev/integrations/output-integrations/data-export/zapier.md
  - https://docs.reo.dev/developers/how-to-find-inbound-developers-in-reo.dev.md
  - https://docs.reo.dev/install-the-tracking-snippet-with-google-tag-manager.md
  - https://docs.reo.dev/integrations/output-integrations/data-export/webhooks.md
  - https://docs.reo.dev/why-a-developer-profile-may-not-be-created-on-reo.dev.md
  - https://docs.reo.dev/developers/interpreting-intel-on-the-developer-dashboard.md
  - https://docs.reo.dev/integrations/input-sources/api-based-integration/lists-api.md
  - https://docs.reo.dev/integrations/input-sources/api-based-integration/custom-product-events-api.md
  - https://docs.reo.dev/getting-started/for-admins/step-3-find-developers-engaging-with-your-product.md
  - https://docs.reo.dev/getting-started/for-users/step-4-identify-developers-engaging-with-your-product.md
  - https://docs.reo.dev/playbooks/for-aes/track-deal-progression-via-developer-intent-in-your-target-accounts.md
servers:
- url: https://ingest.reo.dev
paths:
  /accounts/developer-funnel-stages.md:
    get:
      operationId: get_accounts_developer_funnel_stages_md
      tags:
      - Accounts
      summary: Developer Funnel Stages
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer and relevant
        excerpts from the documentation.
      x-source: https://docs.reo.dev/accounts/developer-funnel-stages.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question to ask the documentation.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The broader goal behind the question.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /api/product/aggregateusage:
    post:
      operationId: post_api_product_aggregateusage
      tags:
      - Api
      summary: POST /api/product/aggregateusage
      x-source: https://docs.reo.dev/integrations/input-sources/api-based-integration/custom-product-events-api/aggregated-events.md
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostApiProductAggregateusageRequest'
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl --location 'https://ingest.reo.dev/api/product/aggregateusage'  --header 'X-API-KEY: <API_KEY>'  --header 'Content-Type:\
          \ application/json'  --data '{\n  \"payload\": {\n    \"mode\": \"DOMAIN\",\n    \"activity_type\": \"DEMO_LOGIN\",\n    \"source\"\
          : \"PRODUCT_CLOUD\",\n    \"environment\": \"PRODUCTION\",\n    \"event_id\": 1231231232,\n    \"event_at\": 639303296,\n    \"user_id\"\
          : \"\",\n    \"user_id_type\": \"\",\n    \"count\""
  /api/product/usage:
    post:
      operationId: post_api_product_usage
      tags:
      - Api
      summary: POST /api/product/usage
      x-source: https://docs.reo.dev/integrations/input-sources/api-based-integration/custom-product-events-api/single-events.md
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl --location 'https://ingest.reo.dev/api/product/usage'  --header 'X-API-KEY: <API_KEY>'  --header 'Content-Type: application/json'\
          \  --data '{\n    \"payload\": {\n\t\"activity_type\": \"LOGIN_ACTIVITY\",\n\t\"source\": \"PRODUCT_CLOUD\",        \n\t\"environment\"\
          : \"PRODUCTION\",\n        \"user_id\": \"https://www.linkedin.com/in/userid\",\n        \"user_id_type\":\"LINKEDIN\",\n        \"\
          ip_addr\": \"156.59.87.83\",\n        "
  /audiences/developer-audience.md:
    get:
      operationId: get_audiences_developer_audience_md
      tags:
      - Audiences
      summary: Developer Audience
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve answers from the documentation.
      x-source: https://docs.reo.dev/audiences/developer-audience.md
      parameters:
      - name: ask
        in: query
        required: true
        schema:
          type: string
        description: The immediate question to ask the documentation.
      - name: goal
        in: query
        required: true
        schema:
          type: string
        description: The overall goal the user is trying to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /developers.md:
    get:
      operationId: get_developers_md
      tags:
      - Developers
      summary: Developers
      description: Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters to retrieve a direct answer and
        relevant excerpts from the documentation.
      x-source: https://docs.reo.dev/developers.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question, specific and self‑contained, written in natural language.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The user’s ultimate goal, describing the outcome they want to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /developers/how-to-find-inbound-developers-in-reo.dev.md:
    get:
      operationId: get_developers_how_to_find_inbound_developers_in_reo_dev_md
      tags:
      - Developers
      summary: How to Find Inbound Developers in Reo.Dev
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer from the documentation.
      x-source: https://docs.reo.dev/developers/how-to-find-inbound-developers-in-reo.dev.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question, specific and self‑contained, written in natural language.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The user’s ultimate goal, describing the outcome they want to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /developers/interpreting-intel-on-the-developer-dashboard.md:
    get:
      operationId: get_developers_interpreting_intel_on_the_developer_dashboard_md
      tags:
      - Developers
      summary: Interpreting Intel on the Developer Dashboard
      description: Perform an HTTP GET request on the documentation page with the `ask` and `goal` query parameters to retrieve a direct answer
        and relevant excerpts from the documentation.
      x-source: https://docs.reo.dev/developers/interpreting-intel-on-the-developer-dashboard.md
      parameters:
      - name: ask
        in: query
        required: true
        schema:
          type: string
        description: The immediate question, specific and self‑contained, written in natural language.
      - name: goal
        in: query
        required: true
        schema:
          type: string
        description: The broader purpose the user is trying to achieve, helping to tailor the answer.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /getting-started/for-admins/step-3-find-developers-engaging-with-your-product.md:
    get:
      operationId: get_getting_started_for_admins_step_3_find_developers_engaging_with_your_product
      tags:
      - Getting Started
      summary: 'Step 3: Find developers engaging with your product'
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer and relevant
        excerpts from the documentation.
      x-source: https://docs.reo.dev/getting-started/for-admins/step-3-find-developers-engaging-with-your-product.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question, specific and self‑contained, written in natural language.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The user’s ultimate goal, describing the outcome they want to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /getting-started/for-users/step-4-identify-developers-engaging-with-your-product.md:
    get:
      operationId: get_getting_started_for_users_step_4_identify_developers_engaging_with_your_prod
      tags:
      - Getting Started
      summary: 'Step 4: Identify developers engaging with your product'
      x-source: https://docs.reo.dev/getting-started/for-users/step-4-identify-developers-engaging-with-your-product.md
      parameters:
      - name: ask
        in: query
        required: true
        schema:
          type: string
        description: The immediate question, specific and self‑contained, written in natural language.
      - name: goal
        in: query
        required: true
        schema:
          type: string
        description: The user’s ultimate goal, describing the outcome they want to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /install-the-tracking-snippet-with-an-npm-package.md:
    get:
      operationId: get_install_the_tracking_snippet_with_an_npm_package_md
      tags:
      - Install The Tracking Snippet With An Npm Package
      summary: Install the tracking snippet with an NPM package
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer from the documentation.
      x-source: https://docs.reo.dev/install-the-tracking-snippet-with-an-npm-package.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question to ask the documentation engine.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The broader goal the user is trying to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /install-the-tracking-snippet-with-google-tag-manager.md:
    get:
      operationId: get_install_the_tracking_snippet_with_google_tag_manager_md
      tags:
      - Install The Tracking Snippet With Google Tag Manager
      summary: Install the tracking snippet with Google Tag Manager
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer from the documentation.
      x-source: https://docs.reo.dev/install-the-tracking-snippet-with-google-tag-manager.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question to ask the documentation.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The broader goal the user is trying to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /integrations/developer-docs.md:
    get:
      operationId: get_integrations_developer_docs_md
      tags:
      - Integrations
      summary: Developer Docs
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer and relevant
        excerpts from the documentation.
      x-source: https://docs.reo.dev/integrations/developer-docs.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question, specific and self‑contained.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The user’s overall goal, describing the desired outcome.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /integrations/input-sources/api-based-integration.md:
    get:
      operationId: get_integrations_input_sources_api_based_integration_md
      tags:
      - Integrations
      summary: 'Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:'
      x-source: https://docs.reo.dev/integrations/input-sources/api-based-integration.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question, specific and self‑contained.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The user’s overall goal, describing the desired outcome.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /integrations/input-sources/api-based-integration/custom-product-events-api.md:
    get:
      operationId: get_integrations_input_sources_api_based_integration_custom_product_events_api_m
      tags:
      - Integrations
      summary: Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters
      description: The endpoint returns a direct answer to the question and relevant excerpts and sources from the documentation.
      x-source: https://docs.reo.dev/integrations/input-sources/api-based-integration/custom-product-events-api.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question, specific and self‑contained.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The user’s ultimate goal, describing the desired outcome.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /integrations/input-sources/developer-insights.md:
    get:
      operationId: get_integrations_input_sources_developer_insights_md
      tags:
      - Integrations
      summary: Developer Insights
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer and relevant
        excerpts from the documentation.
      x-source: https://docs.reo.dev/integrations/input-sources/developer-insights.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question, specific and self‑contained.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The user’s ultimate goal, describing the desired outcome.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /integrations/output-integrations/data-export/zapier.md:
    get:
      operationId: get_integrations_output_integrations_data_export_zapier_md
      tags:
      - Integrations
      summary: Zapier
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer from the documentation.
      x-source: https://docs.reo.dev/integrations/output-integrations/data-export/zapier.md
      parameters:
      - name: ask
        in: query
        required: true
        schema:
          type: string
        description: The immediate question to ask the documentation.
      - name: goal
        in: query
        required: true
        schema:
          type: string
        description: The broader goal the user wants to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /playbooks/for-aes/track-deal-progression-via-developer-intent-in-your-target-accounts.md:
    get:
      operationId: get_playbooks_for_aes_track_deal_progression_via_developer_intent_in_your_target
      tags:
      - Playbooks
      summary: Track Deal Progression via Developer Intent in your Target Accounts
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer and relevant
        excerpts from the documentation.
      x-source: https://docs.reo.dev/playbooks/for-aes/track-deal-progression-via-developer-intent-in-your-target-accounts.md
      parameters:
      - name: ask
        in: query
        required: true
        schema:
          type: string
        description: The immediate question to ask the documentation.
      - name: goal
        in: query
        required: true
        schema:
          type: string
        description: The broader goal or outcome the user wants to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /why-a-developer-profile-may-not-be-created-on-reo.dev.md:
    get:
      operationId: get_why_a_developer_profile_may_not_be_created_on_reo_dev_md
      tags:
      - Why A Developer Profile May Not Be Created On Reo
      summary: Why a Developer Profile May Not Be Created on Reo.Dev
      description: Perform an HTTP GET request on the URL with the `ask` and `goal` query parameters to retrieve a direct answer and relevant
        excerpts from the documentation.
      x-source: https://docs.reo.dev/why-a-developer-profile-may-not-be-created-on-reo.dev.md
      parameters:
      - name: ask
        in: query
        required: false
        schema:
          type: string
        description: The immediate question, specific and self‑contained, written in natural language.
      - name: goal
        in: query
        required: false
        schema:
          type: string
        description: The user’s overall goal, describing the outcome they want to achieve.
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
components:
  schemas:
    PostApiProductAggregateusageRequest:
      type: object
      properties:
        payload:
          type: object
          properties:
            mode:
              type: string
            activity_type:
              type: string
            source:
              type: string
            environment:
              type: string
            event_id:
              type: integer
            event_at:
              type: integer
            user_id:
              type: string
            user_id_type:
              type: string
            count:
              type: integer
            domain:
              type: string
            ip_addr:
              type: string
            product_id:
              type: string
            user_agent:
              type: string
            meta:
              type: object
              properties:
                property1:
                  type: string
                property2:
                  type: string
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: X-API-KEY
security:
- apiKey: []
tags:
- name: Accounts
- name: Api
- name: Audiences
- name: Developers
- name: Getting Started
- name: Install The Tracking Snippet With An Npm Package
- name: Install The Tracking Snippet With Google Tag Manager
- name: Integrations
- name: Playbooks
- name: Why A Developer Profile May Not Be Created On Reo