AMCS Group

AMCS Group MunicipalAccountChangeBatch API

The MunicipalAccountChangeBatch API from AMCS Group — 1 operation(s) for municipalaccountchangebatch.

GitHub OpenAPI

Operations 1

POST /municipal/municipalAccountChangeBatches Create or update #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/amcs-group/openapi/amcs-group-municipalaccountchangebatch-api-openapi.yml

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/amcs-group:amcs-group-municipalaccountchangebatch-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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

amcs-group-municipalaccountchangebatch-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: AMCS Platform REST Municipal Account Change Batch API
  description: '![latest End points](/amcsrestapi/diagram/endpointslatest.svg)


    # Overview


    ## Who Should Read this Document


    This document contains a technical description of the AMCS Platform REST API. It is intended for:


    · System integrators


    · Customer IT team looking to integrate AMCS Platform with another system


    · Third parties looking to integrate their system with AMCS Platform


    ## Document Scope


    This document introduces the technical aspects of the AMCS Platform REST API. The purpose of this document is to provide readers with detail on how to:


    · Access the REST API


    · Make calls to the API to retrieve, append and update resources


    · Retrieve the incremental changes to a collection


    · Find more detail on the end points that are available from an environment. ## Summary


    AMCS Platform REST API is designed to support the integration of AMCS Platform with other systems. With care and additional infrastructure, the REST API can be used to build functionality on top of Platform but that is not it’s primary purpose. The ‘changes since’ process provides the main means of performing an initial synchronisation of the AMCS Platform and another system, and then keeping them synchronised. Methods are also provided to create and update resources. # Integration Patterns and Tools


    The AMCS Platform provides a number of tools that can be used to connect systems. Care should be taken to match the right tooling to the intended pattern of integration. · When an extract-based approach is needed, use BI reporting. · When derived values are require, use the data mart. · When business processes on different systems need to be integrated by synchronising the data on each through an event style interface, use the REST API. An integration using the REST API will need to take full responsibility for all aspects of the integration including:


    · Pulling change events from AMCS Platform


    · Filtering the changed resources for the ones that are of interest


    · Pulling additional resources from the REST API in order the retrieve all the properties needed by the destination


    · Mashing resources to create the complete view required


    · Translating that into the form required by the destination


    · Validating this to ensure it meet the entry rules of the destination


    · Pushing the result to the destination


    In the early stages of designing the interface care should be taken to ensure that the need for caching/staging has been considered. The changes since functionality is effectively a means of pulling create/change events from platform. The only filters available enable retrieval of related resources to build a view external to AMCS Platform


    # Basics


    The AMCS REST API provides a RESTful interface that allows access to the primary business resources of the AMCS platform. The interface follows general HATEOAS compliance principles. ## Quick start


    A quickstart walkthrough based on node.js and covering authentication and getting a page of customers can be found here. ## Interface definitions


    Swagger documentation for the end points available on an environment can be found at:


    Before 8.5: https://{environment domain name}/swagger/ui/index


    From 8.5: https://{environment domain name}/erp/api/swagger/ui/index


    ## HTTP Interface


    The following HTTP RESTful methods are provided as part of this API:


    · GET: Provides read access to retrieve details of one or more resources. · POST: Creates or updates a single resource or a set of resources. · PUT: Updates a single resource or a set of resources. Note:


    · DELETE methods are currently not provided as part of the API. The REST API URIs begin with


    https://{environment domain name}/erp/api/integrator/erp


    For example:

    https://prod.amcs-at-mycompany.com/erp/api/integrator/erp


    This should be used as the base of the URI.'
  version: latest
servers:
- url: https://ete-p5-tst-svc-core.amcsplatform.com/erp/api/integrator/erp
tags:
- name: MunicipalAccountChangeBatch
paths:
  /municipal/municipalAccountChangeBatches:
    post:
      tags:
      - MunicipalAccountChangeBatch
      summary: Create or update
      description: '| Property | Description | Required |

        | ------------------------------------- | ----------------------------------------------------------------------------- | -------- |

        | MunicipalAccountChanges[0]| List of Municipal Account Changes. | Yes |

        | MunicipalAccountChanges[0].MunicipalityListItem| The GUID of the Municipality. | Yes |

        | MunicipalAccountChanges[0].HouseNumber| House Number of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].Address1| Address line 1 of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].Address2| Address line 2 of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].Address3| Address line 3 of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].Address4| Address line 4 of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].Address5| Address line 5 of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].Address6| Address line 6 of Municipal Account. | No |

        | MunicipalAccountChanges[0].Address7| Address line 7 of Municipal Account. | No |

        | MunicipalAccountChanges[0].Address8| Address line 8 of Municipal Account. | No |

        | MunicipalAccountChanges[0].Address9| Address line 9 of Municipal Account. | No |

        | MunicipalAccountChanges[0].Postcode| Post code of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].Latitude| Latitude of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].Longitude| Longitude of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].AddedBy| Who making the change. | Yes |

        | MunicipalAccountChanges[0].MunicipalAccountStateListItem | Current state of Municipal Accout. Required for New account. | Yes |

        | MunicipalAccountChanges[0].MunicipalAccountStatusDate| Account state effective from. Required if state is provided. | Yes |

        | MunicipalAccountChanges[0].MunicipalAccountBuildingTypeListItem| Building type of municipal Account. | Yes |

        | MunicipalAccountChanges[0].Purpose| Purpose of change. | No |

        | MunicipalAccountChanges[0].ExternalReferenceTypeListItem | External refernce type of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].ExternalReference| External refernce of Municipal Account. | Yes |

        | MunicipalAccountChanges[0].OtherInformation| Non-sale end cost for this accounting period inventory. | No |

        | MunicipalAccountChanges[0].FunctionalID| FunctionalID of municipal account to identify create/update. | Yes |


        **Extra validations**


        | Condition| Error message |

        | -----------------------------------------------------------------| ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |

        | If MunicipalityListItem.Guid provided is Deleted.| The provided MunicipalityListItem is deleted. Could not update the resource. Please check the relevant list end point for the available options. |

        | If MunicipalAccountStateListItem.Guid provided is Deleted.| The provided MunicipalAccountStateListItem is deleted. Could not update the resource. Please check the relevant list end point for the available options. |

        | If MunicipalAccountBuildingTypeListItem.Guid provided is Deleted. | The provided MunicipalAccountBuildingTypeListItem is deleted. Could not update the resource. Please check the relevant list end point for the available options. |

        | If ExternalReferenceTypeListItem.Guid provided is Deleted.| The provided ExternalReferenceTypeListItem is deleted. Could not update the resource. Please check the relevant list end point for the available options. |'
      operationId: MunicipalAccountChangeBatch_Create
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ApiIntegratorMunicipalAccountChangeBatchResource'
        required: true
        x-bodyName: null
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiResourceId'
components:
  schemas:
    ApiIntegratorMunicipalAccountChangeBatchResource:
      type: object
      properties:
        MunicipalAccountChanges:
          type: array
          items:
            $ref: '#/components/schemas/ApiIntegratorMunicipalAccountChangeResource'
        GUID:
          type: string
          format: uuid
          example: 00000000-0000-0000-0000-000000000000
    ApiResourceId:
      type: object
      properties:
        resource:
          type: string
          format: uuid
        errors:
          $ref: '#/components/schemas/ApiResourceErrors'
        status:
          $ref: '#/components/schemas/ApiResourceStatus'
    ApiIntegratorListItemResource:
      type: object
      properties:
        Description:
          type: string
        Guid:
          type: string
          format: uuid
          example: 00000000-0000-0000-0000-000000000000
    ApiResourceStatus:
      type: object
      properties:
        id:
          type: integer
          format: int32
        isSuccess:
          type: boolean
    ApiIntegratorMunicipalAccountChangeResource:
      type: object
      properties:
        MunicipalityListItem:
          $ref: '#/components/schemas/ApiIntegratorListItemResource'
        HouseNumber:
          type: string
        Address1:
          type: string
        Address2:
          type: string
        Address3:
          type: string
        Address4:
          type: string
        Address5:
          type: string
        Address6:
          type: string
        Address7:
          type: string
        Address8:
          type: string
        Address9:
          type: string
        Postcode:
          type: string
        Latitude:
          type: number
          format: double
        Longitude:
          type: number
          format: double
        AddedBy:
          type: string
        MunicipalAccountStateListItem:
          $ref: '#/components/schemas/ApiIntegratorListItemResource'
        MunicipalAccountStatusDate:
          type: string
          format: localDate
          example: '2000-01-01'
        MunicipalAccountBuildingTypeListItem:
          $ref: '#/components/schemas/ApiIntegratorListItemResource'
        Purpose:
          type: string
        ExternalReferenceTypeListItem:
          $ref: '#/components/schemas/ApiIntegratorListItemResource'
        ExternalReference:
          type: string
        OtherInformation:
          type: string
        FunctionalID:
          type: string
        CustomerTemplateId:
          type: integer
          format: int32
        OperationalAreaId:
          type: integer
          format: int32
        CompanyOutletId:
          type: integer
          format: int32
        GUID:
          type: string
          format: uuid
          example: 00000000-0000-0000-0000-000000000000
        LastChangeReasonId:
          type: integer
          format: int32
    ApiResourceErrors:
      type: object
      properties:
        errors:
          type: string