FIWARE

FIWARE API Entry Point API

The API Entry Point API from FIWARE — 1 operation(s) for api entry point.

Documentation GitHub OpenAPI

Operations 1

GET /v2 Retrieve API Resources #

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/fiware-api-entry-point-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:
  version: '1.0'
  title: FIWARE-NGSI v2 Specification API Entry Point API
  description: 'TODO: Add a description'
servers:
- url: http://orion.lab.fiware.org/
tags:
- name: API Entry Point
paths:
  /v2:
    get:
      description: 'This resource does not have any attributes. Instead it offers the initial

        API affordances in the form of the links in the JSON body.

        It is recommended to follow the “url” link values,

        [Link](https://tools.ietf.org/html/rfc5988) or Location headers where

        applicable to retrieve resources. Instead of constructing your own URLs,

        to keep your client decoupled from implementation details.'
      summary: Retrieve API Resources
      tags:
      - API Entry Point
      operationId: Retrieve API Resources
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RetrieveApiResourcesResponse'
              example:
                entities_url: /v2/entities
                types_url: /v2/types
                subscriptions_url: /v2/subscriptions
                registrations_url: /v2/registrations
      x-unitTests:
      - request:
          method: GET
          uri: /v2
        expectedResponse:
          x-allowExtraHeaders: true
          x-bodyMatchMode: RAW
          x-arrayOrderedMatching: false
          x-arrayCheckCount: false
          x-matchResponseSchema: true
          headers:
            Content-Type: application/json
          body: '{  "entities_url": "/v2/entities",  "types_url": "/v2/types",  "subscriptions_url": "/v2/subscriptions",  "registrations_url": "/v2/registrations"}'
        x-testShouldPass: true
        x-testEnabled: true
        x-testName: Retrieve API Resources1
        x-testDescription: 'This resource does not have any attributes. Instead it offers the initial

          API affordances in the form of the links in the JSON body.

          It is recommended to follow the “url” link values,

          [Link](https://tools.ietf.org/html/rfc5988) or Location headers where

          applicable to retrieve resources. Instead of constructing your own URLs,

          to keep your client decoupled from implementation details.'
      x-operation-settings:
        CollectParameters: false
        AllowDynamicQueryParameters: false
        AllowDynamicFormParameters: false
        IsMultiContentStreaming: false
components:
  schemas:
    RetrieveApiResourcesResponse:
      title: Retrieve API Resources response
      example:
        entities_url: /v2/entities
        types_url: /v2/types
        subscriptions_url: /v2/subscriptions
        registrations_url: /v2/registrations
      type: object
      properties:
        entities_url:
          description: URL which points to the entities resource
          example: /v2/entities
          type: string
        types_url:
          description: URL which points to the types resource
          example: /v2/types
          type: string
        subscriptions_url:
          description: 'URL which points to the

            subscriptions resource'
          example: /v2/subscriptions
          type: string
        registrations_url:
          description: 'URL which points to the

            registrations resource'
          example: /v2/registrations
          type: string
      required:
      - entities_url
      - types_url
      - subscriptions_url
      - registrations_url