LeanData One Time Routing API

This section describes the endpoints used to trigger 1x Routing for creating a custom orchestration experience, as well as to retrieve the status of the resulting job. When invoked, the 1x Routing endpoint returns basic job metadata—including the jobId—which can be used to check the job’s status. orchestration/v1/one-time-routing — Use this endpoint to invoke 1x routing for a particular SFDC org orchestration/v1/one-time-routing/:jobId — Use this endpoint to retrieve the job status of a 1x routing for a particular SFDC org ❗️ Important: The API does not validate FlowBuilder graphs before triggering routing. If you invoke 1x Routing to an invalid or misconfigured graph, the request will still be processed—but routing will fail silently. No error response will be returned from the API.✅ To avoid unexpected behavior, please ensure the graph is valid and functioning as expected within the LeanData application before using it in API-triggered routing.

Operations 2

POST /orchestration/v1/one-time-routing orchestration/v1/one-time-routing #
GET /orchestration/v1/one-time-routing/:jobId orchestration/v1/one-time-routing/:jobId #

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/leandata-one-time-routing-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

leandata-one-time-routing-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: LeanData Graph One Time Routing API
  description: Run LeanData One Time Routing and fetch routing graph metadata to power custom orchestration solutions and integrations.
  version: 1.0.0
servers:
- url: https://api.leandata.com
tags:
- name: One Time Routing
  description: This section describes the endpoints used to trigger 1x Routing for creating a custom orchestration experience, as well as to retrieve the status of the resulting job.
paths:
  /orchestration/v1/one-time-routing:
    post:
      tags:
      - One Time Routing
      summary: orchestration/v1/one-time-routing
      description: 'Endpoint: POST https://api.leandata.com/orchestration/v1/one-time-routing


        ❗️ Important: The API does not validate FlowBuilder graphs before triggering routing.'
      requestBody:
        content:
          application/json:
            schema:
              type: object
              example:
                objectType: Lead
                condition: Id = '00Q5f000006KnPbEAK'
                graphName: Lead Routing Q2 2025
                notificationsDisabled: false
                nodeType: Trigger
                edgeName: Lead is MQL
                allowDedupe: true
                respectSchedules: true
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: postOrchestrationV1OneTimeRouting
      x-operation-id-source: derived
  /orchestration/v1/one-time-routing/:jobId:
    get:
      tags:
      - One Time Routing
      summary: orchestration/v1/one-time-routing/:jobId
      description: 'Endpoint: GET https://api.leandata.com/orchestration/v1/one-time-routing/:jobId


        This endpoint is used to obtain the status of a One-Time Routing job.


        💡 The :jobId path parameter should be replaced with the unique ID of the One-Time Routing job you want to read.


        Headers


        x-api-key (required) — Your unique API key for authentication.


        Request Body Parameters


        result — An object that contains metadata about the status of the One-Time Routing job.


        completedAt — Timestamp of the job''s completion.


        successCount — A string value representing the number of records that were successfully processed by the routing job.


        nRecords — A string value representing the number of records that were found by the routing job.


        status — A string value representing the status of the One-Time Routing job. Because the API does not validate FlowBuilder graphs, invalid graphs will be marked as "Complete".


        "Complete"


        "Complete with Errors"


        "Canceled"


        "Failed"


        "Processing"


        jobId — A string value that is the unique identifier for the asynchronous One-Time Routing job. You can use this ID to query for the status of the job if such an endpoint is available.'
      responses:
        '200':
          description: Successful response
          content:
            application/json: {}
      operationId: getOrchestrationV1OneTimeRouting:jobId
      x-operation-id-source: derived