Splio Filter API

The Filter API from Splio — 1 operation(s) for filter.

Operations 1

GET /target/filters/{scope} Get filters #

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/splio-filter-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

splio-filter-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Splio Customer Platform Filter API
  description: API Documentation for Splio Customer Platform
  version: 1.0.0
servers:
- url: https://api.splio.com
- url: http://api.splio.com
tags:
- name: Filter
paths:
  /target/filters/{scope}:
    get:
      summary: Get filters
      description: Get filters based on scope.
      parameters:
      - name: scope
        in: path
        required: true
        description: 'Filter scope : contacts, products, stores, orders, baskets, loyalty, rewards.'
        schema:
          type: string
          enum:
          - contacts
          - products
          - stores
          - orders
          - baskets
          - loyalty
          - rewards
      - name: status
        in: query
        required: false
        description: 'Filter status : all, active, inactive, idle, favorite'
        schema:
          type: string
          enum:
          - all
          - active
          - inactive
          - idle
          - favorite
      responses:
        '200':
          description: Filter retrieval is successful.
          content:
            application/json:
              examples:
                response:
                  value:
                    count_element: 1
                    current_page: 1
                    per_page: 50
                    sort: []
                    elements:
                    - intid: 1
                      id: 1
                      name: 'Filter #123'
                      nb_binded_members: null
                      tags:
                      - purchase
                      - sales
                      updated_at: '2025-04-01 00:00:00'
                      status: active
                      is_favorite: false
                      nb_emails: 315
                      nb_sms: 80
                      is_protected: false
        '400':
          description: The request validation failed.
          x-readme: BODYBODY
          content:
            application/json:
              examples:
                response:
                  value:
                    status: 400
                    errors:
                    - error_key: field_1
                      error: wrong_value
                      error_description: The request was malformed and it is unable to be processed. Please review and try again.
        '401':
          description: Authentication failed.
        '403':
          description: Forbidden.
      tags:
      - Filter
      security:
      - Bearer: []
      operationId: getTargetFiltersByScope
      x-operation-id-source: derived
components:
  securitySchemes:
    Bearer:
      description: "For accessing the API a valid JWT token must be passed in all requests in\nthe 'Authorization' header.\n\n\nA valid JWT token is generated by the Authorization API and returned as answer of a call\nto the route /authenticate giving a valid user, password & universe.\n\n\nThe following syntax must be used in the 'Authorization' header :\n\n    Bearer xxxxxx.yyyyyyy.zzzzzz\n"
      type: http
      scheme: bearer
      bearerFormat: JWT
x-origin:
- url: https://api.splio.com/doc.json
  format: swagger
  version: '2.0'
  converter:
    url: https://github.com/mermade/oas-kit
    version: 7.0.8