Equinor Parameters API

The Parameters API from Equinor — 2 operation(s) for parameters.

GitHub OpenAPI
Business capability
Weather & Environment AE-230.10

Operations 2

GET /parameters Returns a list of available parameters to use with parameter sets #
GET /parameters/{name} Retruns information on a specific parameter #

Specifications

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/equinor:equinor-parameters-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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

equinor-parameters-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: StormGeo Parameters API
  description: '# Introduction

    The StormGeo API exposes functionality related to the weather of predefined locations, or given coordinates. The API is available to Equinor users, and certain vendors. The API functions as a gateway to StormGeo''s own weather API, creating a unified way for Equinor users and vendors to access this resource. A simple way to test the API is through Postman which is accessible through AccessIT. # Getting access to the API

    ## Equinor Users

    In order to call the StormGeo API, a client application needs to be configured with API permissions for the StormGeo API. This can be done by performing the following steps:


    1. Create a client app registration in Equinors Azure portal. This step requires the Application Developer role in Access IT. See Omnia documentation Application Management in AAD for more information. 2. Add an API permission for the app registrations towards the StormGeo API prod (client ID = 81707c90-2ec8-4b00-8447-5a5fbbceb3e8). There are two types of permissions that can be added to the app registration in Azure:


    **Delegated permission**: If you want to call the StormGeo API on behalf of the signed-in user in Equinor Entra ID. **Application permission:** If you want to call the API without a signed-in end user. Select the app role named Equinor. 3. Create a client secret for your client app registrations that can be used for authenticating. 4. The last step is to get admin consent for your API access. For delegated permissions this is done by triggering an authentication request, e.g via Postman, which will trigger the consent process. For application permissions, see the Omnia docs for more information. See Authentication and Authorization Overview section for information on how to authenticate. ## External vendors

    External vendors need to have their Equinor contact person request access via this ServiceNow form. **Please note that no SLA is provided on this service from Equinor, hence it cannot be used for critical applications.**


    For every vendor we will setup a an app registration in Equinors Azure tenant and provide the vendor with the client ID. In addition to the client ID, the vendor will need to create a self-signed certificate (maximum 1 year validity) that can be used for authentication, and provide us the public key via the above mentioned ServiceNow request. The same ServiceNow request form can also be used for renewal of certificate. There are several ways to generate a certificate. If you are using Azure this can be done via the Keyvault:


    1. Navigate to the *Keyvault* service in Azure. Select the *Certificates* section in the left hand menu and press the *Generate/Import* button

    !certificate create button


    2. Fill out the fields, similar to this:

    !certificate create fields


    Note the following:


    **CertificateName:** Can be whatever you want. **Subject:** Value is not taken into account when authenticating with a self-signed certificate, but a good practice is to have it match the company name. **Validity Period (in months):** Must not be more than 12 months - otherwise we will reject your certificate. **Content Type:** Can be either PKCS #12 or PEM. PEM is a simpler format and might be easier to deal with. **Lifetime Action Type:** Default choice is *Automatically renew at a given percentage lifetime*. Make sure to change this to one of the notification options instead, so that you can take neccessary steps to have the certificate renewed and send us the new one. 3. Navigate to the certificate in the keyvault, press the *Download in CER format* button and include the downloaded certificate in the ServiceNow request. 4. Make sure to keep the private key (part of the PFX/PEM-file) of the certificate safe, prefferably in the Keyvault itself. Also remember that it is the vendors responsibility to renew the certificate in due time. We don''t accept certificates with a lifetime longer than 1 year.'
  version: v1
servers:
- url: https://api.gateway.equinor.com/stormgeo/v1
tags:
- name: Parameters
paths:
  /parameters:
    get:
      summary: Returns a list of available parameters to use with parameter sets
      description: Returns a list of available parameters to use with parameter sets.
      operationId: get-parameters
      parameters:
      - name: Filters
        in: query
        description: "Filters is a comma-delimited list of {Name}{Operator}{Value} where \n- {Name} is the name of the property. Multiple names (logial OR) can be entered pipe delimited, eg. \"(value1|value2)>10\" will filter items where value1 or value2 is greater than 10.\n- {Value} is the value used for filtering. Multiple values (logial OR) can be entered pipe delimited, eg. \"value@=foo|bar\" will filter items where value contains either \"foo\" or \"bar\".\n- {Operator} is one of the following operators:\n\n| Operator | Name |\n|-|---|\n| == | Equals | \n| != | Not equal | \n| > | Greater than | \n| < | Less than | \n| >= | Greater than or equal to | \n| <= | Less than or equal to | \n| @= | Contains | \n| _= | Starts with | \n| !@= | Does not contain | \n| !_= | Does not start with |"
        schema:
          type: string
      - name: Sorts
        in: query
        description: Sorts is a comma delimited ordered list of proprty names to sort by. Prefix with "-" to sort descending.
        schema:
          type: string
      - name: PageSize
        in: query
        description: Number of items per page. Default no limit.
        schema:
          type: string
      - name: Page
        in: query
        description: Number of page to return. Default 1.
        schema:
          type: string
      responses:
        '200':
          description: Success
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
      tags:
      - Parameters
  /parameters/{name}:
    get:
      summary: Retruns information on a specific parameter
      operationId: get-parameters-name
      parameters:
      - name: name
        in: path
        description: The name of the parameter
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
      tags:
      - Parameters