Erply Event API
The event API from Erply — 1 operation(s) for event.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/erply-event-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
openapi: 3.2.0
info:
description: '## Overview
This application offers an API for managing assignments and tasks.'
title: assignments Event API
contact: {}
version: 2.36.5
tags:
- name: Event
paths:
/api/v1/workorder/{workorderId}/event:
get:
security:
- ErplyClientCode: []
- ErplySession: []
- ErplyJWT: []
- AccessToken: []
description: 'Allows searching for workorder events matching specific criteria.
> Param | Default | Example | Description
> ----------------|---------|---------|----
> `eventType` | | task_created | Event codes that should be returned
> `withTotalCount` | false | true | If total count of matched records should be returned in response header `x-total-count
> `pageSize` | 20 | 100 | Allows specifying how many records per page should be returned
> `pageNr` | 1 | 2 | Allows specifying which page should be returned for creating paginated views over the data.
> `sort` | id | -id | Allows specifying in which order the rows should be returned. Supported values are: `id`. It is possible to reverse the order by adding a `-` prefix to the sorting keyword.
>
>'
tags:
- Event
summary: Look up events
parameters:
- description: Workorder id
name: workorderId
in: path
required: true
schema:
type: integer
- description: Event types
name: eventType
in: query
style: form
explode: false
schema:
type: array
items:
type: string
- description: If total matching record count should be return in response header
name: withTotalCount
in: query
schema:
type: boolean
- description: Result page size
name: pageSize
in: query
schema:
type: integer
- description: Result page number
name: pageNr
in: query
schema:
type: integer
- description: Sorting order
name: sort
in: query
schema:
type: string
responses:
'200':
description: OK
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/EventResponse'
'401':
description: Forbidden
'500':
description: Internal Server Error
operationId: getApiV1WorkorderByWorkorderIdEvent
x-operation-id-source: derived
post:
security:
- ErplyClientCode: []
- ErplySession: []
- ErplyJWT: []
- AccessToken: []
tags:
- Event
summary: Log an event with the workorder
parameters:
- description: Record id
name: workorderId
in: path
required: true
schema:
type: integer
responses:
'201':
description: Created
content:
application/json:
schema:
$ref: '#/components/schemas/EventResponse'
'401':
description: Forbidden
'500':
description: Internal Server Error
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/EventRequest'
description: Event data
required: true
operationId: postApiV1WorkorderByWorkorderIdEvent
x-operation-id-source: derived
components:
schemas:
EventRequest:
type: object
properties:
data:
type: object
eventType:
type: string
workorderId:
type: integer
core.Translatable:
type: object
properties:
ar:
type: string
example: ' '
cs:
type: string
example: ' '
da:
type: string
example: ' '
de:
type: string
example: ' '
default:
type: string
example: ' '
el:
type: string
example: ' '
en:
type: string
example: ' '
es:
type: string
example: ' '
et:
type: string
example: ' '
fi:
type: string
example: ' '
fo:
type: string
example: ' '
fr:
type: string
example: ' '
it:
type: string
example: ' '
lt:
type: string
example: ' '
lv:
type: string
example: ' '
nl:
type: string
example: ' '
'no':
type: string
example: ' '
pl:
type: string
example: ' '
ru:
type: string
example: ' '
sv:
type: string
example: ' '
th:
type: string
example: ' '
tr:
type: string
example: ' '
vi:
type: string
example: ' '
zh_Hans:
type: string
example: ' '
zh_Hant:
type: string
example: ' '
EventResponse:
type: object
properties:
createdAt:
type: string
createdById:
type: integer
data:
type: object
description:
$ref: '#/components/schemas/core.Translatable'
eventType:
type: string
id:
type: integer
workorderId:
type: integer
securitySchemes:
AccessToken:
type: apiKey
name: accessToken
in: header
ErplyClientCode:
type: apiKey
name: clientCode
in: header
ErplyJWT:
type: apiKey
name: jwt
in: header
ErplySession:
type: apiKey
name: sessionKey
in: header
RequestKey:
type: apiKey
name: requestKey
in: header