Engrate Status Request API

The status-request API from Engrate — 1 operation(s) for status-request.

Operations 1

POST /schedule-management/v1/send_status_request Send Status Request #

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/engrate:engrate-status-request-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

engrate-status-request-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Engrate Status Request API
  version: 1.0.0
servers:
- url: https://api.engrate.io
security:
- apiKeyAuth: []
tags:
- name: status-request
paths:
  /schedule-management/v1/send_status_request:
    post:
      description: 'Send a Status Request (SRQ) to a German TSO.


        This is a sort of "reset" functionality, where you can request the TSO re-emits messages for a specified schedule, which will then be re-ingested into Engrate.'
      operationId: send_status_request_schedule_management_v1_send_status_request_post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/StatusRequestCreate'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/StatusRequestResponse'
          description: Successful Response
        '422':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          description: Validation Error
      summary: Send Status Request
      tags:
      - status-request
components:
  schemas:
    StatusRequestCreate:
      additionalProperties: false
      description: Request body for sending a status request to TSO.
      properties:
        date:
          description: 'Delivery date (YYYY-MM-DD). Example: ''2026-01-24''.'
          format: date
          title: Date
          type: string
        sender_id:
          description: Your own EIC X code (balance responsible party, 16-character organization code) as registered with the TSO. Must match the EIC configured for the calling organization.
          title: Sender Id
          type: string
        tso:
          description: 'TSO identifier. DE values: ''50HERTZ_DE_TSO'' (50Hertz), ''DE-AMPRION-TSO'' (Amprion), ''TTG_DE'' (TenneT DE), ''DE-TRANSNETBWTSO'' (TransnetBW).'
          minLength: 1
          title: Tso
          type: string
      required:
      - date
      - sender_id
      - tso
      title: StatusRequestCreate
      type: object
    StatusRequestResponse:
      description: Response from a status request submission to a TSO.
      properties:
        error_message:
          anyOf:
          - type: string
          - type: 'null'
          description: Always `null`. An older version of this endpoint used this for messaging failures; the field is kept for backwards compatibility.
          title: Error Message
        message_id:
          description: Message identifier assigned to the status request.
          examples:
          - SRQ-20260326-100000-A1B2C3D4
          title: Message Id
          type: string
        next_allowed_at:
          anyOf:
          - type: string
          - type: 'null'
          description: Always `null`. An older version of this endpoint had rate limits here, but those are maintained internally now.
          title: Next Allowed At
        sent_at:
          anyOf:
          - type: string
          - type: 'null'
          description: ISO 8601 datetime when the message was queued.
          examples:
          - '2026-03-26T10:00:00+00:00'
          title: Sent At
        status:
          const: queued
          description: Submission lifecycle state. An older version of this endpoint returned other status codes as well, but the only status returned now is `queued`; the field is retained for backwards compatibility.
          title: Status
          type: string
      required:
      - message_id
      - status
      title: StatusRequestResponse
      type: object
    ValidationError:
      properties:
        ctx:
          title: Context
          type: object
        input:
          title: Input
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          title: Location
          type: array
        msg:
          title: Message
          type: string
        type:
          title: Error Type
          type: string
      required:
      - loc
      - msg
      - type
      title: ValidationError
      type: object
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          title: Detail
          type: array
      title: HTTPValidationError
      type: object
  securitySchemes:
    apiKeyAuth:
      in: header
      name: Authorization
      type: apiKey