Prevedere Data Integration API

The Data Integration API from Prevedere — 3 operation(s) for data integration.

Documentation GitHub OpenAPI

Operations 3

GET /clientdimensions Get clientdimensions #

POST /importclientdata/{ClientDimensionGroupId}/{ShouldDeleteExistingRecords} Create importclientdata by client dimension group id by should delete existing… #

POST /validateclientdata/{ClientDimensionGroupId} Create validateclientdata by client dimension group id #

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/prevedere-data-integration-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: Board Foresight API - V1 Data Integration API
  description: ''
  version: v1
security:
- api key: []
tags:
- name: Data Integration
  description: ''
paths:
  /clientdimensions:
    get:
      tags:
      - Data Integration
      description: The complete list of client dimension groups available for data import. Contains dimension and hierarchy information
      parameters:
      - name: request
        in: query
        schema:
          $ref: '#/components/schemas/ClientDimensions'
      responses:
        '200':
          description: OK
        '429':
          description: If the user has sent too many requests
      summary: Get clientdimensions
      x-summary-source: derived
      operationId: getClientdimensions
      x-operation-id-source: derived
  /importclientdata/{ClientDimensionGroupId}/{ShouldDeleteExistingRecords}:
    post:
      tags:
      - Data Integration
      description: 'Imports a client data file into the system. The file should be posted as part of a ''multipart/form-data''-encoded request. Only one file may be posted per request.

        The file should contain all the fields described in the mapping of client dimension group it contains data for, in addition to ''date'', ''measure'' and ''value'' fields.'
      parameters:
      - name: ShouldDeleteExistingRecords
        in: path
        required: true
        schema:
          type: boolean
      - name: ShouldReplaceRecordIfExists
        in: query
        schema:
          type: boolean
      - name: ClientDimensionGroupId
        in: path
        required: true
        schema:
          type: string
      - name: InlineData
        in: query
        schema:
          type: string
      responses:
        '200':
          description: OK
        '429':
          description: If the user has sent too many requests
      summary: Create importclientdata by client dimension group id by should delete existing…
      x-summary-source: derived
      operationId: postImportclientdataByClientDimensionGroupIdByShouldDeleteExistingRecords
      x-operation-id-source: derived
  /validateclientdata/{ClientDimensionGroupId}:
    post:
      tags:
      - Data Integration
      description: 'Validates a client data file against a client dimension group. The file should be posted as part of a ''multipart/form-data''-encoded request. Only one file may be posted per request.

        The file should contain all the fields described in the mapping of client dimension group it contains data for, in addition to ''date'', ''measure'' and ''value'' fields.'
      parameters:
      - name: ShouldDeleteExistingRecords
        in: query
        required: true
        schema:
          type: boolean
      - name: ShouldReplaceRecordIfExists
        in: query
        schema:
          type: boolean
      - name: ClientDimensionGroupId
        in: path
        required: true
        schema:
          type: string
      - name: InlineData
        in: query
        schema:
          type: string
      responses:
        '200':
          description: OK
        '429':
          description: If the user has sent too many requests
      summary: Create validateclientdata by client dimension group id
      x-summary-source: derived
      operationId: postValidateclientdataByClientDimensionGroupId
      x-operation-id-source: derived
components:
  schemas:
    ClientDimensions:
      type: object
      additionalProperties: false
  securitySchemes:
    api_key:
      type: apiKey
      name: ApiKey
      in: query