Even Financial

aid: even-financial
name: Even Financial
description: Engine by MoneyLion (formerly Even Financial) operates an embedded-finance search, comparison and recommendation
  engine for financial services. Its API matches consumers to personalized financial products — personal loans, credit cards,
  savings and deposit accounts, auto refinancing, HELOC and insurance — by submitting a lead (a user plus product search criteria)
  in exchange for a rate table of offers. The platform pairs the native API with embeddable marketplaces, calculators, widgets
  and mobile SDKs, plus approval-probability reports and channel-partner analytics. Even Financial was founded in 2015, backed
  by Canaan Partners, and rebranded to Engine by MoneyLion in 2023 following MoneyLion's acquisition.
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://cdn.prod.website-files.com/65c76d4633ca994639a589c7/65e2220541631373794b6e17_opengraph.png
url: https://raw.githubusercontent.com/api-evangelist/even-financial/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- canaan-partners
x-tier: stub
x-tier-reason: portfolio-lead
x-rebrand: Engine by MoneyLion
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Financial Services
- Embedded Finance
- Fintech
- Lending
- Personal Loans
- Credit Cards
- Marketplace
- Recommendation Engine
- Lead Generation
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: even-financial:even-financial-analytics-api
  name: Even Financial Analytics API
  description: "### Introduction\n\nWelcome to Engine by MoneyLion's Integration Guide for our Supply Analytics data product,\
    \ which provides funnel, payout and client tag data on specific leads and lead segments to better improve your monetization,\
    \ consumer  experience and efficiency of user acquisition.\n\nRefer to [Developer Center](https://engine.tech/developer-center/loans-savings-second-look-marketplace/reporting-options-for-channel-partners/channel-partner-reporting-analytics-api-1)\
    \ for detailed information on how to use this API.\n\nSupply Analytics offers three different reporting endpoints optimized\
    \ for streaming time series datasets out of the Engine by MoneyLion API and into your system via periodic polling, as\
    \ well as an endpoint to obtain a snapshot of all information regarding a single lead. This document contains everything\
    \ needed to understand and integrate with all 4 endpoints offered.\n### API Versions\nThis document describes version\
    \ 3 of the Supply Analytics API. The previous version available to partners is referred to as version 1. Version 2 was\
    \ an internal release.\nAll HTTP requests for this version must include header `API-Version: 2025-04-01`.\n\n### API Endpoints\n\
    \nWe currently offer the following reporting endpoints providing real time insights into the funnel from user acquisition\
    \ through conversion:\n\n1. LeadEvents: This endpoint tracks the lead funnel’s journey. With the Lead Events API, you\
    \ can pull KPI related data for your funnel, measure conversions, and iterate so that you can meet your business goals.\n\
    \n2. LeadPayouts: This endpoint tracks payout by conversion on a per-lead basis.\n\n3. LeadClientTags: This endpoint is\
    \ used to check and confirm which client tags (ie. subID, clickID, or trafficsource) you have appended to each lead (unique\
    \ Engine by MoneyLion generated leadUuid). It provides better customer segmentation and attribution by returning your\
    \ supplied client-tags (key/value) pairs associated with a lead. It's explained with examples in depth in the \"Get  lead\
    \ client tags endpoint\" section.\n\nThe above endpoints can be used to stream information into your system and will be\
    \ referred to as streaming endpoints. Additionally, we have the following endpoint to access an on-demand snapshot of\
    \ lead information:\n\n4. LeadsInfo: This endpoint provides a combined snapshot of information about a single lead — all\
    \ of its events, payouts and client tags in a single request.\n\n### Basic Request to Supply Analytics API\n\nEvery request\
    \ to the Supply Analytics API streaming endpoints will return a JSON object with the following properties:\n\n- `data`\
    \ is the array of objects that should be analyzed / loaded into your\n  database.\n\n- `nextUrl` is the URL that should\
    \ be persisted and used for the next\n  request. It will include a `paginationToken`.\n\n- `shouldContinuePolling` is\
    \ a boolean which signals if calling `nextUrl`\n  will have published data available.\n\n- `paginationToken` is an opaque\
    \ cursor that identifies the end of the\n  current page and is used for the next request. It is already included in\n\
    \  `nextUrl` and also provided separately for convenience.\n\n\nEvents from financial institutions or other external systems\
    \ may not be shared with Engine by MoneyLion for hours or days after they occur; using `paginationToken` ensures that\
    \ backfilled records are not missed.\n\nA response contains all available data subject to the response size limit and\
    \ any applied filters (such as `untilTimestamp`). Requesting a URL with a `sinceTimestamp` that is less than five minutes\
    \ old will return an error, as it can take a few minutes to prepare the response. We suggest polling hourly as a starting\
    \ point, but as long as you follow shouldContinuePolling, you can poll at any interval (>5 minutes). For convenience,\
    \ we provide a `shouldContinuePolling` flag to indicate whether you should continue to poll the Supply Analytics endpoint.\
    \ If `true`, continue with the `nextUrl`. If not, no further data is currently available.\n``` curl -X GET \\\n  'https://api.engine.tech/supplyAnalytics/leadEvents?sinceTimestamp=2019-08-24T14%3A15%3A22Z'\
    \ \\\n  -H 'Accept: application/json' \\\n  -H 'Authorization: Bearer {access-token}' \\\n  -H 'API-Version: 2025-04-01'\n\
    ```\nSince `paginationToken` is initially not known, the initial request may specify the `sinceTimestamp` parameter. In\
    \ the absence of both of them, the endpoint will start with the oldest record in the system. The `nextUrl` from response\
    \ will only include `paginationToken`.\n### Developer's Note About Time Zones\nTimestamps without an explicit timezone\
    \ (timezones missing a suffix of `Z`, for example) are interpreted as UTC. However, we recommend passing an explicit timezone\
    \ offset of Z in the timestamp query string parameter. All timestamps in responses, whether in the event as a field, or\
    \ in the `nextUrl`, are UTC.\n### Developer's Note About Flexible JSON Objects\nEngine by MoneyLion's goal is to enrich\
    \ the data provided by the Supply Analytics endpoint over time to improve your insight and analytical abilities. Therefore,\
    \ it is recommended that any integration or initial setup be created with the future possibility of additional data fields\
    \ in mind. These will take the form of additional JSON keys. We'd recommend that your integration remain compatible if\
    \ there are additional JSON key-values present. This will allow new rollouts and improvements to the supply analytics\
    \ endpoint to happen as smoothly as possible.\n### Backfilling\nWhen backfilling, the `sinceTimestamp` of your initial\
    \ request URL should be to your starting point. You should request each subsequent URL in succession until you're caught\
    \ up. You can use `untilTimestamp` to define the end time of backfill windows.\n\n### Resources\nPartners can contact\
    \ their assigned Engine by MoneyLion Partner Manager or partnersupport@engine.tech for help."
  humanURL: https://engine.tech/docs/api-reference/
  baseURL: https://api.engine.tech
  tags:
  - Analytics
  properties:
  - type: OpenAPI
    url: openapi/even-financial-analytics-api-openapi.yml
  - type: APIReference
    url: https://engine.tech/docs/api-reference/
- aid: even-financial:even-financial-approval-probability-api
  name: Even Financial Approval Probability API
  description: 'Approval probability reports contains data about the likelihood that a user with specified attributes will
    be approved for particular product offers.


    The user attributes are passed in the request''s `POST` body. Attributes are specific to the product in questions and
    do not include personally identifiable information.


    The approval probabilty data is calculated per financial institution, as well as across the entire Engine by MoneyLion
    network. Within each of these groups, offer probablilities may be further broken down according to product attributes.
    For loans, for example, approval probabilities are associated with offer APR range and optionally product sub-type.'
  humanURL: https://engine.tech/docs/api-reference/
  baseURL: https://api.engine.tech
  tags:
  - Approval Probability
  properties:
  - type: OpenAPI
    url: openapi/even-financial-approval-probability-api-openapi.yml
  - type: APIReference
    url: https://engine.tech/docs/api-reference/
- aid: even-financial:even-financial-lead-api
  name: Even Financial Lead API
  description: 'A lead combines information about a user with search criteria for financial products, and is submitted in
    exchange for a rate table.


    A rate table is a list of financial offers that match a submitted lead.


    ### Lead Details


    No fields are required on a lead, but depending on the type of product requested, a minimum subset is required in order
    to potentially receive personalized offers. For details, see [the Financial Products overview](https://engine.tech/docs/api-reference/#financial-products).


    A lead may request multiple product types, in which case the returned rate table will include a list for each product
    type with matching offers.


    ### Asynchronous Rate Tables


    Often a rate table will be built asynchronously. This means that although the rate table gets returned, the API may still
    be waiting for responses from one or more financial institutions. In these cases, you should poll the rate table until
    all responses are resolved before displaying the offers to the end user.


    So, if you submit a lead via the "Submit lead" endpoint and the returned rate table has a non-empty `pendingResponses`
    array, you should reload the rate table via the "Get rate table" endpoint, and continue to do so until `pendingResponses`
    is empty.'
  humanURL: https://engine.tech/docs/api-reference/
  baseURL: https://api.engine.tech
  tags:
  - Lead
  properties:
  - type: OpenAPI
    url: openapi/even-financial-lead-api-openapi.yml
  - type: APIReference
    url: https://engine.tech/docs/api-reference/
- aid: even-financial:even-financial-offer-preview-api
  name: Even Financial Offer Preview API
  description: 'Preview offers are matched based upon a simple set of anonymous criteria and as a result are not personalized.
    This is useful if you''d like to display offers without requesting personalized data. For example, you can improve a search
    experience by presenting example offers to the user prior to asking more detailed questions.


    Offers returned by these endpoints are identical to those that would be included in a rate table. But keep in mind that
    they are not personalized, and it''s a better user experience to ultimtely present personalized offers to a user.'
  humanURL: https://engine.tech/docs/api-reference/
  baseURL: https://api.engine.tech
  tags:
  - Offer Preview
  properties:
  - type: OpenAPI
    url: openapi/even-financial-offer-preview-api-openapi.yml
  - type: APIReference
    url: https://engine.tech/docs/api-reference/
- aid: even-financial:even-financial-prefill-api
  name: Even Financial Prefill API
  description: The Prefill API from Even Financial — 2 operation(s) for prefill.
  humanURL: https://engine.tech/docs/api-reference/
  baseURL: https://api.engine.tech
  tags:
  - Prefill
  properties:
  - type: OpenAPI
    url: openapi/even-financial-prefill-api-openapi.yml
  - type: APIReference
    url: https://engine.tech/docs/api-reference/
- aid: even-financial:even-financial-ui-utils-api
  name: Even Financial UI Utils API
  description: A collection of endpoints that can be used to improve a search experience.
  humanURL: https://engine.tech/docs/api-reference/
  baseURL: https://api.engine.tech
  tags:
  - UI Utils
  properties:
  - type: OpenAPI
    url: openapi/even-financial-ui-utils-api-openapi.yml
  - type: APIReference
    url: https://engine.tech/docs/api-reference/
common:
- type: DeveloperPortal
  url: https://even-financial.gitbook.io/developer-center
- type: Documentation
  url: https://engine.tech/docs
- type: APIReference
  url: https://engine.tech/docs/api-reference/
- type: GettingStarted
  url: https://even-financial.gitbook.io/developer-center/native-api-integrations/credit-cards-marketplace/getting-started
- type: Blog
  url: https://engine.tech/blog
- type: Support
  url: https://engine.tech/contact
- type: GitHubOrganization
  url: https://github.com/EVENFinancial
- type: TermsOfService
  url: https://engine.tech/about/legal#terms
- type: PrivacyPolicy
  url: https://engine.tech/privacy
- type: StatusPage
  url: https://status.engine.tech
- type: Authentication
  url: authentication/even-financial-authentication.yml
- type: DomainSecurity
  url: security/even-financial-domain-security.yml
- type: AgenticAccess
  url: agentic-access/even-financial-agentic-access.yml
- type: Packages
  url: packages/even-financial-packages.yml
- type: SDKs
  url: packages/even-financial-packages.yml
- type: LLMsTxt
  url: llms/even-financial-llms.txt
- type: MCPServer
  url: mcp/even-financial-mcp.yml
- type: Conventions
  url: conventions/even-financial-conventions.yml
- type: ErrorCatalog
  url: errors/even-financial-problem-types.yml
- type: Lifecycle
  url: lifecycle/even-financial-lifecycle.yml
- type: ChangeLog
  url: changelog/even-financial-changelog.yml
- type: Components
  url: components/even-financial-components.yml
- type: DataModel
  url: data-model/even-financial-data-model.yml
- type: Conformance
  url: conformance/even-financial-conformance.yml
- type: Webhooks
  url: asyncapi/even-financial-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Arazzo
  name: Submit a lead and retrieve its rate table
  url: arazzo/even-financial-submit-lead-rate-table.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence